diff options
| author | tv <tv@krebsco.de> | 2026-11-05 00:19:12 +0100 |
|---|---|---|
| committer | tv <tv@krebsco.de> | 2026-11-05 00:19:12 +0100 |
| commit | 26d41bef0de3a0d8f25b62776e966ed464a34063 (patch) | |
| tree | 4729050cb69859cbf4b1c2e88be6c9fd72f990db /docs/peers.md | |
| parent | 5ace906873fc5d1757a86b016b5e731ab5decf1a (diff) | |
offer again ungenerated
Diffstat (limited to 'docs/peers.md')
| -rw-r--r-- | docs/peers.md | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/docs/peers.md b/docs/peers.md index fc4b6f1..eb1eb5c 100644 --- a/docs/peers.md +++ b/docs/peers.md @@ -165,7 +165,8 @@ may not arrive within the transport's delivery limit (Mycelium's five minutes). as it knows them). The peer fetches them as a blob, in chunks, from the sender and any other peer holding those 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. This is how a join without a +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 recent remake, or a return after much was written, gets the bulk of its changes. A node downloads one delta at a time: while a large one comes, it lacks those changes, so its other neighbours offer them too, and they would come once per offer. Offers that come |
