Expand description
The device side of an exchange: tokens, retained responses, and cursors.
The engine performs no I/O and runs no ULCP command. It reads an arriving request, decides whether the request needs to be executed at all, and hands the caller the embedded frame together with where in a continued read to resume. The caller dispatches that frame through whatever machinery serves its local link and reports what came back; the engine wraps it, hands it out, and retains it against a retransmission.
Authorization is not the engine’s concern: a request reaches it only after its source has been checked against the administrator list.
Structs§
- Device
Engine - The device half of the Node Management binding.
- Dispatch
- A request the engine wants executed.
- Produced
- What dispatching a frame produced.
Enums§
- Complete
Error - Why a response could not be assembled.
- Drop
Reason - Why an arriving payload produced nothing.
- Ingress
- What the caller must do with an arriving payload.
Constants§
- CACHE_
ENTRIES - Retained entries the reference engine keeps, one per administrator.
Type Aliases§
- Public
Key - An Ed25519 public key naming a node.