We've kept the FlashSocket option in there, as it ultimately means the user gets the benefit of a WebSocket connection without native WebSocket support; a singl

We've kept the FlashSocket option in there, as it ultimately means the user gets the benefit of a WebSocket connection without native WebSocket support; a single bidirectional connection resulting in the lowest latency possible. Our HTTP fallback offers XHR Streaming, XHR Long-polling, IFRAME options (streaming, polling htmlfile etc.) and JSONP-polling for older browsers. The preference is of course a WebSocket connection, then streaming (as it means a persistent connection is created), then long-polling, then standard polling. The problem with any sort of polling is that it's generally inefficient and there are periods of time where a connection isn't established - this means data on the client may not be the most up to date (stale). We all know: WebSocket FTW! :)