Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add support for websocket_tail output #296

Open
muhlpachr opened this issue Oct 11, 2019 · 2 comments
Open

Add support for websocket_tail output #296

muhlpachr opened this issue Oct 11, 2019 · 2 comments
Labels
enhancement outputs Any tasks or issues relating specifically to outputs

Comments

@muhlpachr
Copy link

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 ?

@Jeffail
Copy link
Collaborator

Jeffail commented Oct 12, 2019

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.

@Jeffail Jeffail added enhancement outputs Any tasks or issues relating specifically to outputs labels Oct 12, 2019
@muhlpachr
Copy link
Author

@Jeffail yes, if there are multiple clients connected, I would like to broadcast message to all of them like https://github.com/allinurl/gwsocket.

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 ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement outputs Any tasks or issues relating specifically to outputs
Projects
None yet
Development

No branches or pull requests

2 participants