Expand description
The control-plane client transport.
Lives here rather than in the daemon so there is exactly one implementation of “send an op, read the answer”, and so a test or an agent can drive a running daemon by linking this crate instead of shelling out to the CLI.
The op types are in rusty_time-api, shared with wasm and the future mesh
transport; this transport is native-only. Which transport a --control
argument resolves to is decided by rusty_time_api::control_endpoint, so
the daemon and this client always agree.
Functions§
- default_
path - Where the control plane lives by default. Defined in
rusty_time-apiso the daemon and this client cannot disagree. - request
- Send one op to a running daemon and read its answer.