sockjs/sockjs-client — Issue #44: In Sockjs 0.2 safari doesn't use websockets
Author: majek
Created: 2012-01-27 15:05:35+00:00
State: open

It looks that since 0.2 Safari is less likely to use websockets and more often falls back to xhr-polling.

This may be caused by general slowness of safari, or safari websockets implementation.

For example, connecting to host in the same network takes about 14ms in safari and 4ms in chrome.