We fixed using a reliable transport communication which Bundles, Compresses and Delivers the data more efficiently. Check it out! https://github.com/pubnub/pubnub-api/tree/master/websocket - PubNub WebSocket Emulation
PubNub offers full RFC 6455 Support for WebSocket Client Specification. PubNub WebSockets enables any browser (modern or not) to support the HTML5 WebSocket standard APIs. Use the WebSocket Client Directly in your Browser that Now you can use new WebSocket anywhere!
While emulating WebSocket on non-supporting browsers is definitely awesome, the point I am making, is I am using a websocket-supported browser yet it's just doing a series of non-stop HTTP requests.
Shouldn't the emulation only occur when necessary and be a graceful degradation not forcing all clients to downgrade to a less efficient transport?