ReconnectingWebSocket

Does not even back off. I like the idea of offering libraries that provide some abstraction over standard libraries, but what's the use if it's just the most trivial solution that's unusable for any production situation?

Always important because our beloved websockets are fragile!<p>socket.io has it built in, but in various projects I had to hoist my own reconnect functionality on top because reconnects kept failing.<p>engine.io aims to be more reliable than socket.io, mainly due to connecting via the fallback methods first, then establishing a websocket connection. I have not used e.io yet but intend to soon.<p><a href="http://stackoverflow.com/questions/9610951/how-is-engine-io-different-from-socket-io" rel="nofollow">http:&#x2F;&#x2F;stackoverflow.com&#x2F;questions&#x2F;9610951&#x2F;how-is-engine-io-...</a>

Socket.io is a decent WebSocket wrapper which also reconnects, and of course has lots of other features.

One of the nice things about EventSource (server-sent events) is that it reconnects by default, and error recovery logic is handled by the browser.

This seems a bit naive. No ping&#x2F;pong, no mention of what happens to messages in transit when the connection drops.

No tests?

That&#x27;s what I use. Works as advertised. Should be part of the spec I think.