Skip to main content

Module messages

Module messages 

Source
Expand description

Wire messages: typed builders for what an adapter sends, checked parsers for what it receives.

The adapter pushes commits, the driver issues requests, and either side may send an error and close. Everything is validated against the active limits before it is retained; failures are returned, never raised.

Structs§

AdapterInfo
Identifies the adapter implementation to the driver.
GetTree
The driver asking for a tree: the latest, or a held revision.
GetTreeResult
Answers a GetTree with exactly one of a snapshot or an error.
Hello
The adapter’s handshake: sent exactly once, before anything else.
HelloAck
The driver’s reply: session id, negotiated limits, what to push.
LogBudget
The log-channel allowance, sent only when the adapter announced the logs capability. Absent means logs are disabled: an adapter that receives no budget must not emit log messages at all.
LogMessage
Carries one application log record to the driver.
MarkerConfig
Whether the adapter should emit render markers.
ProbeInfo
What a probe says about itself when it attaches.
ProtocolErrorMessage
Terminal error: the sender closes after emitting it.
RevisionCommit
Announces that a render was committed to the terminal.
SnapshotMessage
Carries a full tree for one revision.

Enums§

ProbeIdentityKind
How an object’s identity behaves across frames.

Constants§

PROTOCOL_ID
The wire protocol identifier both sides must agree on.
PROTOCOL_V2_ID
Qualified observation protocol identifier.
PROTOCOL_VERSION
The current major version.

Functions§

default_capabilities
Every capability a tree-publishing adapter with real bounds announces.
parse_adapter_message
Validate one adapter → driver message.
parse_driver_message
Validate one driver → adapter message.