arora-bridge 3.0.0

The Arora Bridge trait: the connection between an Arora runtime and a remote (e.g. Semio Studio), modelled on studio-bridge's device-client.

Documentation

Coverage
77.55%
38 out of 49 items documented0 out of 20 items with examples
Size
Source code size: 28.57 kB This is the summed size of all the files inside the crates.io package for this release.
Documentation size: 1.22 MB This is the summed size of all files generated by rustdoc for all configured targets
Ø build duration
this release: 11s Average build duration of successful builds.
all releases: 12s Average build duration of successful builds in releases after 2024-10-23.
Links
Homepage
semio-ai/arora-sdk
1 0 14
crates.io
Dependencies
Versions
Owners

arora-bridge

The live-control link of Arora: how a running device is reached from the outside.

A Bridge carries three streams between the device and a remote — device-info updates, a data-interest toggle, and commands — plus send_data to push state changes out. Commands are BridgeOps: read keys (Get), apply a state change (Update), call a function (Call), and introspect what exists (ListKeys, ListMethods — the live-edit surface).

The runtime answers commands against its state and engine, one per step, and replies through the command's channel. FakeBridge is the no-op implementation for offline runs; Semio Studio's Zenoh connector and Vizij's WebSocket server are real ones.

Part of the device runtime interfaces, with arora-hal and arora-behavior.