sockjs-client

I'm using SockJS (client and server: https://github.com/sockjs/sockjs-client) for project I'm working on, which does implement a variety of fallback methods (iframe tricks, JSON polling, etc.) and it's been working pretty well (some work better than others.) For those who to opt for these libs, I recommend the following for protocols/fallbacks: protocols_whitelist: ['websocket', 'xhr-streaming', 'iframe-eventsource', 'iframe-htmlfile', 'xhr-polling', 'iframe-xhr-polling'] This gets you a working system in pretty much every modern browser supporting WS, and /usually/ works pretty well in IE8/9. Just try to avoid page refreshes in those two browsers (very spotty results if you don't - I'd recommend putting up a message for your users) and implement the workarounds for finicky browsers (things

Shameless plug: SockJS[1] is a client and server library that tries to be a WebSockets poly-fill. Basically, you can start using SockJS right now, write code using WebSockets API, and replace SockJS with native websockets when they're ready. So, with SockJS websockets are basically working. There is no reason to wait. [1] https://github.com/sockjs/sockjs-client

<shameless plug> That's exactly what I thought and that's why SockJS is there: https://github.com/sockjs/sockjs-client a) start using SockJS b) wait until enough browsers supports it c) drop SockJS. SockJS has a websocket-like API so no need to do major code changes when you switch. </shameless plug>