diff options
| author | Mathias Buus <mathiasbuus@gmail.com> | 2016-03-15 15:45:50 -0700 |
|---|---|---|
| committer | Mathias Buus <mathiasbuus@gmail.com> | 2016-03-15 15:45:50 -0700 |
| commit | bc9a93217576005fc4428e1cf4c0131cc1095162 (patch) | |
| tree | 9d53a8ef591817336f31f08b5e311601f61713a1 | |
| parent | b113dcb8d353b3a915d4d33d852553e58f659cf8 (diff) | |
| download | dat-docs-bc9a93217576005fc4428e1cf4c0131cc1095162.tar.gz dat-docs-bc9a93217576005fc4428e1cf4c0131cc1095162.zip | |
add inspiration note
| -rw-r--r-- | hyperdrive.md | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/hyperdrive.md b/hyperdrive.md index 293f8c5..999a03c 100644 --- a/hyperdrive.md +++ b/hyperdrive.md @@ -14,6 +14,8 @@ It also tries to be modular and export responsibilities to external modules when Prioritized synchronization of parts of a feed is also at the heart of hyperdrive as this allows for fast streaming with low latency of data such as structured datasets (wikipedia, genomic datasets), linux containers, audio, videos, and much more. To allow for low latency streaming another goal is also to keep verifiable block sizes as small as possible - even with huge data feeds. +The protocol itself draws heavy inspiration from existing file sharing systems such as BitTorrent and [PPSP](https://datatracker.ietf.org/doc/rfc7574/?include_text=1) + ## How Hypercore works ### Flat Trees |