This is an implementation of the server side part of SockJS
SockJS enables browsers to communicate with the server using a simple WebSocket-like api for sending and receiving messages. Under the bonnet SockJS chooses to use one of several protocols depending on browser capabilities and what appears to be working across the network.
Available protocols include:
This means, it should just work irrespective of what browser is being used, and whether there are nasty things like proxies and load balancers between the client and the server.
For more detailed information on SockJS, see their website.
You can register multiple applications with the same SockJSServer, each using different path prefixes, each application will have its own handler, and configuration.
Instances of this class are not thread-safe.
no subtypes hierarchy
|Attributes inherited from: |
Install an app which bridges the SockJS server to the event bus
Close the server
Set a EventBusBridgeHook on the SockJS server
|Methods inherited from: |