Expand description
Replicated designer transactions. The operation set is the durable state: materialization is deterministic regardless of transport order, and local undo submits a new compensating write. A host supplies authentication, authorization, durable storage and delivery; this crate does not open a socket or execute arbitrary code.
Structs§
- Collaboration
Error - Conflict
- Cursor
- Document
Replica - Ordered operation-set replication of a lossless XAML document. Property writes are last-writer wins in Lamport order; structural conflicts are explicit and resolved in that same order. A transaction arriving before its inserted-node dependency is retained and retried when the dependency arrives. No server order or wall-clock synchronization is required.
- Merge
Report - Operation
- Operation
Id - A causal Lamport timestamp with deterministic actor/sequence tie-breaking. Actor identifiers must be unique per durable writer; persist a writer’s sequence or use a new actor after restart.
- Presence
- Snapshot
- A complete transport-independent checkpoint. Exact baseline comparison prevents a snapshot from being accidentally merged into a session based on different source text.
- Sync
Message
Enums§
- Shared
Edit - Each operation is one atomic transaction. A source replacement is compare-and-set: it is never allowed to silently erase unrelated concurrent edits. Structural commands use the source-preserving AST engine and are re-evaluated after out-of-order delivery.
- Shared
Node Id - Names are shared across replicas, unlike process-local AST node numbers.
Constants§
- MAX_
DOCUMENT_ BYTES - MAX_
MESSAGE_ BYTES - MAX_
OPERATIONS - MAX_
PRESENCE_ ACTORS - MAX_
SNAPSHOT_ BYTES - Checkpoints retain several wire batches, without allowing an unbounded operation log.
- PROTOCOL_
VERSION
Type Aliases§
- Result
- Version
Vector - Highest contiguous sequence received per actor. Gaps do not advance a peer’s summary; replay synchronization may resend later operations, which are idempotently deduplicated.