aboutsummaryrefslogtreecommitdiffstats
path: root/src/remake/api.rs
diff options
context:
space:
mode:
authortv <tv@krebsco.de>2026-11-14 12:15:16 +0000
committertv <tv@krebsco.de>2026-11-14 12:15:16 +0000
commit6a87b812fe65dfb23dc21d7634de3b6e58344322 (patch)
tree5aff510a35efa566fd1bf053a8b55a367be12558 /src/remake/api.rs
parent9c9dd8ad7a339be4434efee9bb6c0d144b1a8c91 (diff)
federation: what it asks of the document, and where Automerge sets limits
The design leaned on Automerge in places it didn't say: writers that cost memory, one change per writer and number, changes Automerge applies and shouldn't, the order of values written at once, maps made at one key, history held in memory, bytes that versions must agree on. A section near the start says what the design asks of the document, and nothing else of it is read: changes named by their hashes, each judged at its history; the document at a set of changes, the same on every node; a writer for each change; history kept as long as the store keeps it, and remakes. A section at the end says, for each of Automerge's seven limits, what Automerge does, what the design does about it, and what would go without it. Every rule that is there only for one of them points to it in place. "Writer" is the design's word for the identity a node writes under; "actor" stays with Automerge.
Diffstat (limited to 'src/remake/api.rs')
0 files changed, 0 insertions, 0 deletions