You can clone with
HTTPS or Subversion.
Nope, live qunit tests aren't deployed any more, sorry.
Mention the ietf/hybi email thread about WS over ssl stability
@nyarly updated SockJS-Ruby
Update README, goodbye sockjs-lua, hello sockjs-go!
Added lacking installation step for sockjs-node
Cosmetic - sockjs works better over ssl
Mention @njoyce fork of sockjs-gevent
#94 - SockJS is more stable over SSL
Merge branch 'master' of github.com:sockjs/sockjs-client
npm --dev doesn't behave
Merge branch 'dev' of github.com:sockjs/sockjs-client into dev
Merge branch 'master' into dev
Note on Heroku
more ws rfc links
Added IE 10, updated RFC6455 implementations
Suggest using SockJS 0.3 not 0.2
Don't mention heroku, mention https Europe.
Note that non-SSL connection may not work from SSL-served page.
Try to be more helpful and mention a bug in README.
Fix #49 - Support for sockjs-client being used from pages served from…
… file:// addresses
Mention raw websocket url in the readme
Link to the source about the connections per domain restriction.
Mention SockJS behaviour on browsers blocking third party cookies.
Mention other sockjs related projects
Mention https in readme
Mention problems with file:// urls
Apparently \xFFFE and \xFFFF aren't valid unicode characters
Readme updated to 0.2