Skip to main content

Module transport

Module transport 

Source
Expand description

ClientTransport + LocalTransport (PLAN-phase2 §2.7).

LocalTransport is the in-process client: same Runtime, same StreamEvent values moved through a channel, never serialised. The socket flavour (SocketTransport, B2) implements the same trait.

Structs§

BinaryId
Which binary a process runs: its version and build (binary_version, build_id); the build is empty when unknown.
LocalTransport

Enums§

TransportError

Constants§

ATTACH_TIMEOUT
Attach handshake budget.
ATTACH_TIMEOUT_PARKED
Attach budget when the listed lifecycle is Parked (unpark ≤ 20 s, B3).

Traits§

ClientTransport

Functions§

version_skew_notice
When a client binary differs from the daemon it talks to: what to tell the user, else None. An attached TUI keeps its own binary across daemon reload (only the daemon re-execs), so after an upgrade it lacks every client-side change — new slash commands, tray fixes, new events — until it is restarted. Builds count, not just versions: a reload onto a newer build of the same release is the common case. An unknown build (empty: older daemon, packaged build) compares by version only.