aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorMax Ogden <max@maxogden.com>2016-02-09 16:06:47 -0800
committerMax Ogden <max@maxogden.com>2016-02-09 16:06:47 -0800
commita35fd8e89c83c1ca019806f4bc1acc07feae59a3 (patch)
tree89ca4c0106d588664f27fcf9ac7b1787ce373a8a
parentf9001ead2f38a0f429b6c717875b3bbaf8cdea6b (diff)
downloaddat-docs-a35fd8e89c83c1ca019806f4bc1acc07feae59a3.tar.gz
dat-docs-a35fd8e89c83c1ca019806f4bc1acc07feae59a3.zip
typo
-rw-r--r--how-dat-works.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/how-dat-works.md b/how-dat-works.md
index 2087c82..0e3d13c 100644
--- a/how-dat-works.md
+++ b/how-dat-works.md
@@ -34,6 +34,6 @@ The short version of how Hyperdrive works is that it breaks file contents up in
We use a technique called Rabin fingerprinting to break files up into pieces. Rabin fingerprints are a specific strategy for what is called Content Defined Chunking. Here's an example:
-![meta/cdc.png]
+![cdc diagram](meta/cdc.png)
When two peers connect to each other and begin speaking the Hyperdrive protocol they can efficiently determine if they have chunks the other one wants, and begin exchanging those chunks directly. Hyperdrive gives us the flexibility to have random access to any portion of a file while still verifying the other side isnt sending us bad data. We can also download different sections of files in parallel across all of the sources simultaneously, which increases overall download speed dramatically.