Expand description
The registration handshake (blueprint §7.3).
node daemon
├──────── Hello / Welcome ─────────────────►│ (§7.2, astrs-transport)
├──────── Register(NodeHandshake) ─────────►│
│◄─────── Registered { spec, session } ─────┤
├──────── Subscribe { inputs } ────────────►│
│ │
└──────── the pump starts here ─────────────┘The handshake runs on the link before the reader task exists, because
everything after it depends on the specification Registered carries: a
path: dynamic node (§8.3) has no ASTRS_NODE_CONFIG at all and learns
its wiring here, and even a spawned one takes the daemon’s word for its
generation over its own.
§Events that arrive during the handshake
A daemon may legitimately send an input the instant it accepts the
registration — it is under no obligation to wait for Subscribe. Those
frames are buffered here and replayed through the ordinary dispatcher
once the queues exist, so a message can be early but never lost.
Structs§
- Registration
- What the registration produced.
Constants§
- REGISTRATION_
TIMEOUT - How long the registration exchange waits for its answer.
Functions§
- register
- Registers over an established link and starts the session.
- register_
with register, told where the daemon’s segment broker listens (§6.2).