There are 2 pieces to this puzzle: Q: Will the client-side portion of “comet” be necessary? A: Yes. Even in the next 2 years, you’re not going to see full support for WebSockets in the “major” browsers. IE8 for example doesn’t have support for it, nor does the current version of FireFox. Given that IE6 … Read more
In HTTP/2 the server pushes to the client a request for the resource with a PUSH_PROMISE frame. While going from server to client, this is not a response, but a request, the request the client would make to fetch that resource. When the client receives the PUSH_PROMISE, it can look at the URI, and figure … Read more
I’m surprised noone here has mentioned long-polling. Long polling means keeping an open connection for a longer period (say 30-60 seconds), and once it’s closed, re-opening it again, and simply having the socket/connection listen for responses. This results in less connections (but longer ones), and means that responses are almost immediate (some may have to … Read more
I wrote the plugin mentioned by Till. The plugin is an implementation of the Bayeux protocol and currently supports long-polling (local server via AJAX) and callback-polling (remote server via XSS). There is a Bayeux implementation for Python called cometd-twisted that I have heard my plugin works with, but I have not verified this. I have … Read more
Put a L3 load-balancer that distributes IP packets based on source-IP-port hash to your WebSocket server farm. Since the L3 balancer maintains no state (using hashed source-IP-port) it will scale to wire speed on low-end hardware (say 10GbE). Since the distribution is deterministic (using hashed source-IP-port), it will work with TCP (and hence WebSocket). Also … Read more