dangernoodle-io / TaipanMiner / 26204242447 / 3

90%

main: 90%

push

github

refactor(webui): multiplex /api/events through a single SseClient (#423)

Each /api/events SSE topic used to open its own EventSource — the
dashboard alone held two persistent sockets (update.available,
block.found) on top of polling, and the pattern was about to grow
linearly as we add more topics. On firmware that's another open socket
per topic counted against CONFIG_LWIP_MAX_SOCKETS, and another
select_cb sitting in httpd_server's select() — both of which have a
known cliff under load (lwip asserts on the freed netconn / select_cb
that breadboard B1-224 hardens against).

Switch to one connection, multiplexed:

- SseClient gains an `eventHandlers: Record<topic, fn>` option that
  registers each topic as a named addEventListener on the underlying
  EventSource. One ES instance = one TCP connection regardless of
  topic count.
- Each state machine (updateAvailableState, blockFoundState) drops its
  own SseClient and exposes a `handleMessage(data)` method plus an
  exported `*_TOPIC` constant.
- App.svelte owns the single SseClient and wires
  { [UPDATE_AVAILABLE_TOPIC]: ..., [BLOCK_FOUND_TOPIC]: ... }.

New topics added to the stream drop into the eventHandlers map without
adding sockets or further fan-out boilerplate.

582 of 1273 branches covered (45.72%)

Branch coverage included in aggregate %.

1461 of 2361 relevant lines covered (61.88%)

12.65 hits per line