This also happens when chrome simply drops the connection even if it is "supported". Chrome 16 and 17 have switched to a newer websocket standard which apparent

This also happens when chrome simply drops the connection even if it is "supported". Chrome 16 and 17 have switched to a newer websocket standard which apparently does not deal with packet loss as well? For now compare with Firefox as well as its Websocket implementation seems to handle a bit better than latest chrome builds in some situations. At the very least we will push out a messaging change for this soon. Once the load spike dies down a bit we will be working to push out some protocol updates to help provide fallback support for browsers that for whatever reason can't maintain a stable websocket connection.