Expand description
The Arora Bridge interface.
A Bridge connects an Arora runtime to a remote — in practice Semio Studio
over studio-bridge. It is modelled on studio-bridge’s device-client
trait: push local state changes out, receive device-info updates and
commands in, and learn when a client is asking for data.
The trait lives here (lean: arora-types + async primitives) so the runtime
can depend on the interface without depending on studio-bridge.
studio-bridge keeps its device-client implementations and provides a
connector that implements this trait.
Structs§
- Bridge
Command - A command received from the remote, carrying a one-shot reply channel.
- Device
Info - Neutral device metadata the bridge syncs with the remote. The bridge-flavored
wire form (studio-bridge’s
PartialDeviceInfo) is converted to/from this by the connector. - Fake
Bridge - A no-op
Bridgefor tests and offline runs: never registers, never emits updates, commands, or claims, and accepts (drops) any data sent.
Enums§
- Bridge
Error - Something went wrong on the bridge.
- Bridge
Op - An operation a remote client asks the device to perform. Mirrors
studio-bridge’s
AroraOp.
Traits§
- Bridge
- The connection between an Arora runtime and a remote (e.g. Semio Studio).
Type Aliases§
- Bridge
Result - Command
Stream - Stream of commands from the remote.
- Data
Requested Stream - Stream of the “a client is asking for data” (claim) toggle.
- Device
Info Stream - Stream of device-info updates.
Ok(None)means the device was unregistered.