Add event‑driven SSE connect/disconnect triggers #3312
Unanswered
SixFive7
asked this question in
Web Server
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Describe the Web Server enhancement
Add event‑driven automation triggers to the web_server component for the built‑in Server‑Sent Events stream (/events, used by the local Web UI):
Goals:
on_client_connected
andon_client_disconnected
triggers) so users can handle Web UI presence the same way they handle API sessions.-Dprotected=public
to readWeb_Server::events_
.Optional trigger variables
path
(string) – the event source path, default "/events".client_info
(string, optional) – a short identifier similar in spirit to the API hook. Avoid IP unless explicitly enabled by the user.Use cases
Current workaround
Why this is not acceptable as a long-term solution:
The proposed event triggers make this hack unnecessary.
Usage examples of proposed solution
Minimal: log when a Web UI tab connects or disconnects
User‑land counter built from events
Raise log level only while a GUI is open
Beta Was this translation helpful? Give feedback.
All reactions