You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+14-16Lines changed: 14 additions & 16 deletions
Original file line number
Diff line number
Diff line change
@@ -289,19 +289,17 @@ Command bytes for operations:
289
289
290
290
The replication process:
291
291
292
-
293
-
294
-
* Check if we have data locally and return if it exists.
295
-
* Downloading starts by sending an ASK request and waiting for a HAS response.
296
-
* After the HAS response the peer will send a series of messages starting with DATA followed by a chunk of the raw data.
297
-
* Once all the data has been sent the peer sends a DONE message and stops replicating the Tunnel.
298
-
* This data stream is ingested into the local Iroh store.
299
-
* Once the data stream is finished we verify the final hash from Iroh.
300
-
* If it does not match the data is thrown out and replication is started with another peer.
301
-
* When replication we first ask for a Repo’s collection hash in order to get the hashes for their file list.
302
-
* Afterwards we may initiate downloads for individual files by first looking up their hash in the collection.
303
-
* Replication connects to peers in the group in random order until one has the data, thus ensuring we don’t need a specific peer to be online as long as somebody has a copy.
304
-
* Implements failure handling with peer fallback \
292
+
* Check if we have data locally and return if it exists.
293
+
* Downloading starts by sending an ASK request and waiting for a HAS response.
294
+
* After the HAS response the peer will send a series of messages starting with DATA followed by a chunk of the raw data.
295
+
* Once all the data has been sent the peer sends a DONE message and stops replicating the Tunnel.
296
+
* This data stream is ingested into the local Iroh store.
297
+
* Once the data stream is finished we verify the final hash from Iroh.
298
+
* If it does not match the data is thrown out and replication is started with another peer.
299
+
* When replication we first ask for a Repo’s collection hash in order to get the hashes for their file list.
300
+
* Afterwards we may initiate downloads for individual files by first looking up their hash in the collection.
301
+
* Replication connects to peers in the group in random order until one has the data, thus ensuring we don’t need a specific peer to be online as long as somebody has a copy.
302
+
* Implements failure handling with peer fallback \
0 commit comments