Skip to content

Commit 50e36f5

Browse files
committed
improve formatting
1 parent bada49e commit 50e36f5

File tree

1 file changed

+14
-16
lines changed

1 file changed

+14
-16
lines changed

README.md

Lines changed: 14 additions & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -289,19 +289,17 @@ Command bytes for operations:
289289

290290
The replication process:
291291

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 \
305303
([Source](https://github.com/rangermauve/veilid-iroh-blobs/blob/default/src/iroh.rs#L450-L550))
306304

307305

@@ -394,10 +392,10 @@ The Save DWeb Backend is built using the Rust programming language, leveraging i
394392

395393

396394

397-
* Run tests with` cargo test`
395+
* Run tests with `cargo test`
398396
* Format code with `cargo fmt`
399-
* Lint with` cargo clippy`
400-
* Run the backend with` cargo run`
397+
* Lint with `cargo clippy`
398+
* Run the backend with `cargo run`
401399

402400
[Source](https://github.com/openarchive/save-dweb-backend/blob/main/README.md#running)
403401

0 commit comments

Comments
 (0)