Install an app which bridges the SockJS server to the event bus
Install an app which bridges the SockJS server to the event bus
The config for the app
A list of JSON objects which define permitted matches for inbound (client->server) traffic
A list of JSON objects which define permitted matches for outbound (server->client) traffic
JSON object holding config for the EventBusBridge
Install an app which bridges the SockJS server to the event bus
Install an app which bridges the SockJS server to the event bus
The config for the app
A list of JSON objects which define permitted matches for inbound (client->server) traffic
A list of JSON objects which define permitted matches for outbound (server->client) traffic
Default time an authorisation will be cached for in the bridge (defaults to 5 minutes)
Address of auth manager. Defaults to 'vertx.basicauthmanager.authorise'
Install an app which bridges the SockJS server to the event bus
Install an app which bridges the SockJS server to the event bus
The config for the app
A list of JSON objects which define permitted matches for inbound (client->server) traffic
A list of JSON objects which define permitted matches for outbound (server->client) traffic
Default time an authorisation will be cached for in the bridge (defaults to 5 minutes)
Install an app which bridges the SockJS server to the event bus
Install an app which bridges the SockJS server to the event bus
The config for the app
A list of JSON objects which define permitted matches for inbound (client->server) traffic
A list of JSON objects which define permitted matches for outbound (server->client) traffic
Install an application
Install an application
The application configuration
A handler that will be called when new SockJS sockets are created
Set a EventBusBridgeHook on the SockJS server
Set a EventBusBridgeHook on the SockJS server
The hook
Helper method wrapping invocations and returning the Scala type, once again to help provide fluent return types
Helper method wrapping invocations and returning the Scala type, once again to help provide fluent return types
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.
On the server side, you interact using instances of org.vertx.scala.core.sockjs.SockJSSocket - this allows you to send data to the client or receive data via the org.vertx.scala.core.sockjs.SockJSSocket.dataHandler().
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.