-
Notifications
You must be signed in to change notification settings - Fork 848
WebSockets support #12
Comments
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. |
Server side making, wrong, assumptions about web socket connecting should not mean we don't get this functionality. |
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 |
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. |
Fair enough, sounds good to me. |
@zackbloom @nilskp check out joewalnes/reconnecting-websocket#1, a model for general purpose WebSocket monitoring / recovery. |
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.
The text was updated successfully, but these errors were encountered: