diff options
| author | tv <tv@krebsco.de> | 2026-11-05 04:00:14 +0100 |
|---|---|---|
| committer | tv <tv@krebsco.de> | 2026-11-05 04:00:14 +0100 |
| commit | f0ef5c33998964d21c5cf5c582cd194327429003 (patch) | |
| tree | 726357c373a0145716f1ee0ec00bfd769b5a934b /docs | |
| parent | f7ce22ed0ba4a758bdc7de0f21b6d0cb45a866b1 (diff) | |
deflate blob chunks
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/peers.md | 5 |
1 files changed, 3 insertions, 2 deletions
diff --git a/docs/peers.md b/docs/peers.md index a6b69b4..e098b01 100644 --- a/docs/peers.md +++ b/docs/peers.md @@ -172,8 +172,9 @@ sent: it would be all or nothing, sent again whole after a lost copy, and on a s may not arrive within the transport's delivery limit (Mycelium's five minutes). The sender takes it back and offers a *delta* instead: the changes in the history of its heads but not of the peer's (as far as it knows them; of those, the ones it holds, and for any it lacks, the heads they -share). The peer fetches them as a blob, in chunks, from the sender and any other peer -holding both sets of heads (every such peer produces the same bytes), loads them, +share). The peer fetches them as a blob, in chunks (each deflated where that makes it +at least a tenth smaller), from the sender and any other peer holding both sets of +heads (every such peer produces the same bytes), loads them, and syncs on; the rest goes in ordinary messages. Until the peer answers, the sender sends it nothing; if the answer is overdue, it offers again (the same offer, without generating the message again, while neither side's heads moved). This is how a join without a |
