Under the hood SockJS tries to use native WebSockets first. If that fails it can use a variety of browser-specific transport protocols and presents them through WebSocket-like abstractions.
SockJS is intended to work for all modern browsers and in environments which don’t support WebSocket protcol, for example behind restrictive corporate proxies.
- SockJS-node Node.js server
- SockJS-erlang Erlang server
- SockJS-lua Lua/Luvit server
- SockJS-tornado Python/Tornado server
- vert.x Java/vert.x server
Work in progress: