Expand description
The sans-IO event/action model.
The protocol core is pure: it consumes Events and produces Actions,
with no device, threads, or clock of its own. The driver loop executes the
actions against a CaDevice and feeds events back. This
keeps every state machine deterministic and testable without
hardware — a test (or a differential comparison against an external
reference) drives a sequence of events and asserts the emitted action
sequence.
Enums§
- Action
- An output the driver loop must perform.
- Event
- An input to the protocol core.
- Host
Request - A request the host application makes of the stack.
- MmiEvent
- MMI (man-machine interface) host events.
- Notification
- A host-facing event surfaced by the stack (the useful outputs of a CI session — what an application reacts to).