From 8b1f40dc8027dd01eccb35aac73ae6ebcd752fa3 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Alexander=20Schn=C3=B6rch?= Date: Sat, 7 Nov 2026 22:03:05 +0100 Subject: [PATCH] docs(design): 047 exact-topic subscribes now send a snapshot (#438) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The exact-topic exception in §3.1 is superseded by #438. Co-Authored-By: Claude Opus 5.5 --- docs/design/047-retire-ws-protocol-converge-on-aimx.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/design/047-retire-ws-protocol-converge-on-aimx.md b/docs/design/047-retire-ws-protocol-converge-on-aimx.md index 7af8f13e..009a324e 100644 --- a/docs/design/047-retire-ws-protocol-converge-on-aimx.md +++ b/docs/design/047-retire-ws-protocol-converge-on-aimx.md @@ -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.