Please check the build logs for more information.
See Builds for ideas on how to fix a failed build, or Metadata for how to configure docs.rs builds.
If you believe this is docs.rs' fault, open an issue.
tear-client — typed RPC client for tear-daemon.
Connects over UDS locally, over SSH/mosh-tunneled UDS remotely.
Speaks the same typed MultiplexerControl trait the daemon
implements — connection mode is the only difference visible to
the consumer.
Shape
[Client] holds a parking_lot::Mutex<UnixStream>. Each
MultiplexerControl call:
- Acquires the mutex.
- Writes a length-prefixed bincode [
Request]. - Reads a length-prefixed bincode [
Response]. - Decodes the response variant into the trait's return type.
The mutex serialises requests within one Client. Multiple
Clients connected to the same daemon get their own connections
and proceed in parallel — that's how mado will scale across
Tier-2/Tier-3 callers without head-of-line blocking.
Why sync
The trait is sync. The PTY pump is on the daemon side, not the client side. Async at this layer would be all cost no benefit — the client's job is to ferry a few Request/Response pairs per human keystroke, not pump kilobytes per second.