Expand description
The console’s live streams (SRV-011 R1 and R2).
The server publishes them as the participant liminal.<device> on the
ordinary transport:
console.topology (one full topology record per change event; a reader’s
snapshot is the stream’s latest record) and console.tap.<target> (one
record per tap batch for the node or stream <target>).
Nothing here reads a store row: the topology is built from the channel roster and the responder registry the server already holds, and the tap is fed at the publish return.
Re-exports§
pub use counts::ConsoleCountsSnapshot;pub use error::ConsoleError;pub use hub::ConsoleHub;pub use hub::MAX_LIVE_TAPS;pub use hub::PumpReport;pub use hub::TAP_SUBJECT_PREFIX;pub use hub::TOPOLOGY_SUBJECT;pub use hub::tappable;pub use model::FlowRole;pub use model::ThisDevice;pub use model::TopologyChange;pub use model::TopologyModel;pub use publisher::ServerPublisher;pub use readings::Origin;pub use readings::READINGS_SUBJECT;pub use readings::Reading;pub use readings::ReadingValue;pub use readings::ReadingsRecord;pub use readings::Source;pub use readings::TargetKind;pub use records::StationActivity;pub use topology::ChannelNode;pub use topology::TopologySnapshot;pub use topology::snapshot;
Modules§
- counts
- The console’s counters.
- error
- What a console stream operation can fail with.
- hub
- The console hub the connection services own (SRV-012 R4, R6, R7, R9).
- model
- The topology the server holds in memory (SRV-012 R7).
- publisher
- Where the console’s records go.
- readings
- The console’s readings (SRV-015 R1): numbers the map can be wired to, on
their own subject,
console.readings. - records
- The console’s records, in the field names of the console’s own reader.
- topology
- The topology document (SRV-011 R1), built from in-memory state only.
- wall
- The one wall-clock reading the console’s records are timed from.