HTTP request associated with the upgrade to web sockets connection
Processing configuration
Authorize this web socket handshake to proceed
Authorize this web socket handshake to proceed
Maximum size of web socket frames. Defaults to 100K.
Optional callback executed when the handshake is successfully completed. You can use this callback to register the web socket client as being ready to receive data.
Optional callback executed when the websocket is closed. The closed web socket id is passed to method
Comma separated list of supported protocols.
Comma separated list of supported protocols. e.g. chat, stomp
Processing configuration
Processing configuration
Netty channel associated with this request
Netty channel associated with this request
Timestamp when this event was fired
Timestamp when this event was fired
Number of milliseconds from the time when this context was created
Number of milliseconds from the time when this context was created
HTTP end point
HTTP end point
Indicates if this web socket handshake is authorized or not
Store of items that can be used to pass data from route to processor and between processors.
Store of items that can be used to pass data from route to processor and between processors.
This map is not synchronized and not thread-safe. In most cases, we expect this cache to be used by a single thread - hence a standard map is faster.
If you do need to use a thread safe map, from your route, instance and store a ConcurrentHashMap
as an item
in this cache.
Maximum size of frames for this web socket connection in bytes.
HTTP request associated with the upgrade to web sockets connection
Callback for when the web socket is closed
Callback for when the handshake as completed
Incoming HTTP request
Always s set to null
because no response is available for handshakes.
Always s set to null
because no response is available for handshakes. Let the handshaker do the work for you.
Username of the authenticated user.
Username of the authenticated user. You need to set this for it to appear in the web logs.
Socko does not make assumptions on your authentication method. You do it and set this username
to let
us know.
Unique ID for this web socket connection
Unique ID for this web socket connection
With Netty 5, we can use ChannelId. However, this is not supported in Netty 4 so we'll have to use a combination of the UUID and the object hash code.
Adds an entry to the web log
Adds an entry to the web log
HTTP status code
length of response content in bytes
Event fired when performing a web socket handshake to upgrade a HTTP connection to a web socket connection.
Socko requires this event be processed in your route and NOT passed to actors. The only action that needs to be taken is to call
event.authorize()
.Calling
event.authorize()
authorizes Socko to perform all the necessary handshaking. If not called, Socko will reject the handshake and web sockets processing will be aborted.event.authorize()
is a security measure to ensure that upgrades to web socket connections is only performed at explicit routes.HTTP request associated with the upgrade to web sockets connection
Processing configuration