Expand description
Generic sans-IO request/reply engine.
Callers submit ops, move bytes with Engine::poll_transmit and
Engine::handle_input, drive time with Engine::handle_timeout, and
read results from Engine::poll_event. A Protocol expands each op
into Steps and classifies replies; the engine keeps exactly one step
in flight, abandons the rest of an op on its first failure, and reports
progress after every completed step.
Structs§
- Engine
- The engine: it runs a
Protocol’s ops one step at a time, sans IO. See the module’s documentation. - Step
- One message to send and the reply that completes it.
Enums§
- OpError
- Why an op failed.
whatnames the step (“program write”) andindexits slot, when it has one. - Outcome
- How a received message relates to the step in flight.
Traits§
- Protocol
- A synth’s request/reply rules.