Expand description
Managing a device over the mesh, from a node.
Exchange knows the binding and nothing else: it hands out payloads
to send and reads the ones that come back. This binds it to a
[PeerConnection], so an administrator’s operation becomes a matter of
servicing it until it finishes.
The node layer delivers packets from inside the coordinator’s borrow,
so a response is queued where it arrives and read where it can be
acted on. The caller owns the clock and the pump: it services the
exchange, then drives its Host until the deadline the service call
named, whichever comes first.
Structs§
- Node
Manager - One administrator’s dealings with one device.
Enums§
- Begin
Error - Why an operation could not be started.
- Management
Error - Why an outstanding exchange could not be carried further.
- Progress
- What the caller should do next.
Constants§
- REPLY_
MAX - How large a reply this reassembles before giving up.