Expand description
The long-lived bridge server.
A WebSocket plane the browser connects to and an HTTP control plane the
operator drives, joined by an id-keyed correlator.
A request flows: control plane (authenticated) → assign id + register a
oneshot waiter → serialise a Command frame → WebSocket → browser
fetch() → BrowserReply frame → correlator resolves the waiter by id
→ control plane returns the HTTP response.
Structs§
- Bridge
Config - Resolved runtime configuration for a bridge instance.
Functions§
- run
- Binds both planes (fail-closed) and serves until the process is stopped.