You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Would you consider to add WebSocket output with functionality alike https://github.com/allinurl/gwsocket (allowing message trashing in case there is not any client) to be able to watch/check stream output just from web browser please ?
The text was updated successfully, but these errors were encountered:
Hey @muhlpachr, if there are multiple clients connected would you expect messages to be broadcast to all of them?
There's a possibility of adding an output mechanism to wrap http_server, where if it doesn't accept a transaction the message is dropped, which would get you partially there. However, I'd need to implement a different mechanism for publishing messages to N clients.
It would be nice to be able to do that without additonal component like gwsocket.
I do understand, that adding (publishing over http server) client JavaScript terminal together with WebSocket is not usual stream processing output. I consider it useful for troubleshooting and debugging.
Streaming through HTTP GET is limited by web browser timeouts for GET and it also do not reconnect autonomously from web browser in case of connectivity troubles.
What kind of wrap for http_server do you mean please ?
Would you consider to add WebSocket output with functionality alike https://github.com/allinurl/gwsocket (allowing message trashing in case there is not any client) to be able to watch/check stream output just from web browser please ?
The text was updated successfully, but these errors were encountered: