Skip to content

docs(design): 047 exact-topic subscribes now send a snapshot (#438) #441

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
lxsaah merged 2 commits into from
Nov 7, 2026
Merged

docs(design): 047 exact-topic subscribes now send a snapshot (#438) #441

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
8b1f40d
docs(design): 047 exact-topic subscribes now send a snapshot (#438)
lxsaah Nov 7, 2026
b1021fa
Merge branch 'main' into docs/047-exact-topic-snapshots
lxsaah Nov 7, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs/design/047-retire-ws-protocol-converge-on-aimx.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -114,8 +114,8 @@ registration, which would be its own design.
skipped (logged), matching "subscribe to what can stream". A wildcard that
matches nothing yields an empty stream that ends immediately — with a
frozen record set, "no matches now" is "no matches ever". Exact-topic
subscribe keeps its existing fast path and (unchanged) emits no snapshot
on the UDS/serial/TCP paths.
subscribe keeps its existing fast path. *Superseded by #438:* it now also
emits a snapshot of the record's current value, as WebSocket does.
- Core stays pull-per-record (no fan-out bus — no_std targets must not pay a
per-record pump); the WS server's `ClientManager` bus keeps per-event
pattern matching for many-client fan-out.
Expand Down
Loading