Skip to content
This repository has been archived by the owner on Jul 10, 2024. It is now read-only.

WebSockets support #12

Open
fungiboletus opened this issue Oct 30, 2013 · 6 comments
Open

WebSockets support #12

fungiboletus opened this issue Oct 30, 2013 · 6 comments

Comments

@fungiboletus
Copy link

Do you manage to add a WebSockets monitoring in addition to the Ajax monitoring ?

Maybe a proxy in front of the browser websockets API is necessary. Anyway, a «send again the websockets messages» feature would be fantastic.

@zackbloom
Copy link
Contributor

Hmmm, interesting. It's pretty complex to do though, as we'd have to reopen the socket after the connection is restored, and many servers are set up to do something when a connection is initiated, so it is not going to work perfectly out-of-the-box in every situation.

@nilskp
Copy link

nilskp commented Nov 6, 2013

Server side making, wrong, assumptions about web socket connecting should not mean we don't get this functionality.

@zackbloom
Copy link
Contributor

Is it a wrong assumption to assume a client is connecting when you get a client opening a connection?

I'm happy to review a PR, if you'd like to make one @nilskp

@nilskp
Copy link

nilskp commented Nov 6, 2013

Well, it's wrong to assume that a WebSocket connection is so stable that a client is never dropped and thus never needs to reconnect. I don't know in which universe that would be a good assumption.

@zackbloom
Copy link
Contributor

Fair enough, sounds good to me.

@mygzi
Copy link

mygzi commented Nov 14, 2013

@zackbloom @nilskp check out joewalnes/reconnecting-websocket#1, a model for general purpose WebSocket monitoring / recovery.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants