Module admin 

The administrator side of an exchange: token choice, retransmission pacing, and the cursor continuation loop.

The engine performs no I/O. It hands the caller payloads to send and reads the payloads that come back; the caller owns the transport, the clock, and the buffer the read reassembles into.

One Exchange serves a whole operation, which may span several request/response round trips when a read does not fit one payload. An administrator MUST NOT have more than one exchange outstanding with a given device, so one of these per device is the whole bookkeeping.

Structs

Exchange

One operation against one device.

Reassembly

A buffer a continued read reassembles into.

Enums

Failure

How an exchange ended.

Outcome

A finished exchange.

Step

What the caller should do next.

Constants

MAX_ATTEMPTS

Retransmissions before an exchange is abandoned. Four attempts across half a minute is long enough for a multi-hop path to recover and short enough that a person waiting on it gets an answer.

RETRY_MS

How long to wait for a response before retransmitting, matching the request pacing umsh-text settled on for the same mesh.