fix: use explicit /peer/counter channel for streaming-counter
The 'default' relay channel accumulated stale Source connections from previous sessions, causing frame delivery issues to Receivers on /stream/default. Moving counter to an explicit /peer/counter channel (matching clock, stats, mood pattern) fixes the composition dashboard. All 4 streams now show live data: Count: 3, Doubled: 6.
This commit is contained in:
parent
8775860fdd
commit
442a2db65e
2 changed files with 2 additions and 2 deletions
|
|
@ -16,7 +16,7 @@
|
|||
--
|
||||
-- Open the built file in a browser.
|
||||
|
||||
let counter = stream from "ws://localhost:9100/stream/default"
|
||||
let counter = stream from "ws://localhost:9100/stream/counter"
|
||||
let clock = stream from "ws://localhost:9100/stream/clock"
|
||||
let stats = stream from "ws://localhost:9100/stream/stats"
|
||||
let mood = stream from "ws://localhost:9100/stream/mood"
|
||||
|
|
|
|||
|
|
@ -10,7 +10,7 @@ let count = 0
|
|||
let doubled = count * 2
|
||||
let message = "Streaming Counter"
|
||||
|
||||
stream counter on "ws://localhost:9100" { mode: signal, output: count, doubled }
|
||||
stream counter on "ws://localhost:9100/peer/counter" { mode: signal, output: count, doubled }
|
||||
|
||||
view counter =
|
||||
column [
|
||||
|
|
|
|||
Loading…
Add table
Reference in a new issue