Crate aequora_protocol

Expand description

Stable wire data-transfer objects for synchronization exchanges.

Modules§

wire_limits: Absolute allocation ceilings enforced while deserializing untrusted transport DTOs. Deployments normally configure lower runtime limits in aequora-validator and transports.

BootstrapRequest: Request to begin or resume a consistent snapshot bootstrap.
BootstrapResponse: One resumable page from a consistent bootstrap snapshot.
ClientLimits: Client-enforced response limits advertised to the server.
Conflict: A stale-base conflict surfaced to the client.
OperationAck: Result retained by the server operation ledger and returned for retries.
OperationEnvelope: A domain operation and the synchronization metadata needed to process it safely.
OperationKind: Numeric identifier registered by an application for an operation payload.
OperationMetadata: Metadata that is useful to the application but independent of its payload.
OperationRejection: A permanent operation rejection that should not be retried unchanged.
Partition: One opaque partial-synchronization partition selector.
PushHint: Payload-free notification that prompts a client to use the normal pull protocol. Hints are advisory and never carry authoritative business state.
RemoteChange: An authoritative journal entry pulled by a client.
SessionMetadata: Authenticated session metadata sent on every exchange.
SnapshotEntity: One authoritative entity in a consistent bootstrap snapshot.
SnapshotLimits: Client limits for one bootstrap snapshot page.
SyncRequest: One bidirectional push/pull synchronization request.
SyncResponse: One response containing push results and incremental pull changes.

Capability: A feature that can be negotiated additively.
ChangeKind: Kind of authoritative state transition.
ConflictPolicy: Conflict behavior selected by application policy.
PushHintReason: Reason a server suggests that the client perform a normal synchronization exchange.
RejectionCode: Stable machine-readable rejection categories.
ResyncReason: Reason incremental synchronization must restart from a consistent snapshot.
SyncDirective: Typed server instruction accompanying every synchronization response.