Expand description
Nested message and enum types in V1.
Structs§
- Catchup
Complete - Sent once per Mutate that adds subscriptions (a catch-up “wave”), after the wave’s last TopicsLive: everything the Mutate asked for is delivered.
- Messages
- A batch of new messages; group and welcome messages share the stream, depending on which subscriptions are active.
- Started
- The first frame on every stream.
- Topics
Live - Emitted when topics finish catch-up, AFTER the last history frame for them — including any live messages that queued up behind the catch-up, which were equally historical from the client’s perspective — so every later frame for a listed topic is live tail. Informational only: delivery correctness (no duplicates, no gaps) never depends on it. Re-adding a topic re-runs catch-up and re-emits it; receivers treat it idempotently.
Enums§
- Capability
- Optional per-stream protocol features (none defined yet; future revisions add values, e.g. fetch-over-stream lookups answered with the same read view that feeds the stream, or new streamable topic kinds).
- Response