Expand description
Agent lifecycle: everything between a configuration and a running robot —
sockets, candidate discovery, certificate, QUIC endpoint, the session
Engine, signaling, and the maintenance that keeps all of it alive
(port-mapping lease renewal, certificate rotation, network-change
re-gather).
seydd and seyd-ffi are both hosts of this type. A host supplies media
(push_video, push_message), consumes AgentEvent, and owns nothing of
the lifecycle itself — which is what keeps the daemon and the SDK from
drifting apart. Anything a host does differently (where frames come from,
where commands go, how the publisher is told to reconfigure) stays in the
host; anything that must be identical everywhere lives here.
Structs§
- Agent
- A running robot agent. Cheap to clone; every clone refers to the same agent.
- Agent
Config - How a robot is configured, independent of where that configuration came
from —
seydd.toml, a Cseyd_config, or a test.
Enums§
- Agent
Event - What a running agent tells its host. The engine’s own events pass through unchanged; the rest describe the lifecycle the host no longer runs itself.