diff options
| author | tv <tv@krebsco.de> | 2026-11-19 17:44:03 +0000 |
|---|---|---|
| committer | tv <tv@krebsco.de> | 2026-11-19 19:26:01 +0100 |
| commit | 59e889254b1fda2dcc8e3e6d596635d1b77f589f (patch) | |
| tree | 2412dd262e7ae729498eb3300912395b601cd0b6 /docs/guides/federation | |
| parent | 180aba9ff89a4a294e284aa281d96adbcfe1b85b (diff) | |
transport: wire versions spoken side by side
A build speaks wire versions OLDEST to VERSION and writes each node the
newest both speak (wire::choose), as the node's SPEAKS says; the oldest
until it says. The identity layer keeps that per address (Book::speaks):
a SPEAKS from an address sets it for the address, and for every address
of the node proven there, and a new address of a node takes it over.
Paths encodes each message for an address in its version
(Transport::encode_in; Transport::encode is the newest).
So that two nodes know what the other speaks once they have proven
themselves to each other, before any other message goes between them, a
SPEAKS goes ahead of every WHO and ME, and WHO and ME are read in every
version from 52 on (wire::PROOFS): their tags and layout never change.
Without that, a node whose oldest version is past the other's couldn't
read its proofs, and the two would never get to the handshake that says
what each speaks. A SPEAKS naming no version this build speaks is logged
as a message of another version is, naming the node to upgrade, the
versions as ranges.
A 0.0.1 node takes a SPEAKS from an address not yet proven for any other
message from there: it drops it, and asks WHO.
This build speaks 52 alone, so nothing it sends changes but the SPEAKS
ahead of the proofs. A release adding a version encodes and decodes the
older ones from their own, frozen, types.
Diffstat (limited to 'docs/guides/federation')
| -rw-r--r-- | docs/guides/federation/upgrades.md | 9 |
1 files changed, 5 insertions, 4 deletions
diff --git a/docs/guides/federation/upgrades.md b/docs/guides/federation/upgrades.md index 6ffde67..9025164 100644 --- a/docs/guides/federation/upgrades.md +++ b/docs/guides/federation/upgrades.md @@ -10,10 +10,11 @@ design's ([`federation.md`](../../federation.md), A node of a federated swarm upgrades as any node does ([`operations.md`](../../operations.md), [Upgrading](../../operations.md#upgrading)), restarted with its files, and a release's version says how: a patch or a minor release one -node at a time, a major one every node close together. Across a change of the wire -format, a major one, upgraded nodes and the others don't talk, and the swarm is split -until all are upgraded; a remake needs the same Automerge on every node, and one with -another rejoins instead of switching. Before 1.0.0, take every upgrade as a major one. +node at a time, a major one every node close together. Nodes write each other the newest +wire version both speak; where two releases share none, a major one, upgraded nodes and +the others don't talk, and the swarm is split until all are upgraded. A remake needs the +same Automerge on every node, and one with another rejoins instead of switching. Before +1.0.0, a release's tag says whether it is a flag day. Nobody runs every node of a federated swarm: each party's operators upgrade its nodes. A patch or minor release each party takes when it likes; for a major one, agree on when, |
