Closed bradgessler closed 12 years ago
Added transport fail-overs on the client-side. If WS can't connect, this will resort to long polling.
I'm not going to worry about this on the server side because Safari is using an old version of the WS spec. Assume that will be upgraded to the final draft over time.
This is really a haproxy/web standards problem because safari uses a WS spec that doesn't work with haproxy.