Serge S. Koval

Error handling

1

I was doing some internal tests and here's what I found. 1. There's `sockjs_session_sup` supervisor which is configured to have up to 10 failures in 10 seconds. 2. sockjs_session calls...

Experimental buffer flushing after session was closed

3

Few notes: 1. Not sure if it should check response_pid from the state. 2. I tried it locally with different transports - appears to be working

I think it'll be great to treat /xhr_send to closed connection same as if session wouldn't exist and return 404 error code instead of silently ignoring messages. I found bug...

Reconnection logic does not work if TCP connection closes

3

Reconnection logic implemented in #236 does not cover case when TCP connection to the server getting closed as a result of server crash. Steps to reproduce: 1. Run this server...

Whoops :-)