Channel by which the request entered and response will be written
The initial HTTP request
Incoming data for processing
Web Socket configuration
Channel by which the request entered and response will be written
Channel by which the request entered and response will be written
Close the web socket connection
Web Socket configuration
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 used by this chunk
HTTP end point used by this chunk
The initial HTTP request
Indicates a binary frame
Indicates a text frame
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.
Web socket version
Returns the request content as byte array
Returns the request content as a string.
Returns the request content as a string. UTF-8 character encoding is assumed
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.
Sends a binary web socket frame back to the client
Sends a binary web socket frame back to the client
Binary data to return to the client
Sends a text web socket frame back to the client
Sends a text web socket frame back to the client
Text to send to the client
Adds an entry to the web log.
Adds an entry to the web log.
Web logs were designed for request/response style interaction and not the duplex communication channel of websockets.
By default, Socko does not write web logs for websocket frames. This is because Socko does not know the context of your frames. However, you can write web logs by calling this method from your route or actor processor.
If you have authenticated the user, you can set it in this.username
.
Can be used to describe the operation or the message type. No spaces allowed.
Can be used to provide context. Querystring is also permissible.
Length of request frame. Set to 0 if none.
Status code
Length of response frame in bytes. Set to 0 if none.
Incoming data for processing
Event fired when a web socket text or binary frame is received.
A org.mashupbots.socko.events.WebSocketFrameEvent will only be fired after an initial org.mashupbots.socko.events.WebSocketHandshakeEvent has been successfully processed.
Channel by which the request entered and response will be written
The initial HTTP request
Incoming data for processing
Web Socket configuration