Socko events are raised by Socko and passed into your routes for dispatching to your handlers. Socko events provides a bridge between Netty and Akka.
org.mashupbots.socko.events.HttpChunkEvent - Fired when a HTTP chunk is received. Typically only used with large request data such as file upload.
org.mashupbots.socko.events.WebSocketHandshakeEvent - Fired prior to a web socket handshake to establish a web socket connection.
org.mashupbots.socko.events.WebSocketFrameEvent - Fired when a WebSocket text or binary frame is received.
HTTP request message for the current event (as opposed to an initial HTTP required to triggered a HTTP Chunk or web socket event).
Identifies the end point associated with the firing of an event.
Identifies the end point associated with the firing of an event. In Socko terminology, an end point comprise the request method, host, path and query string.
HTTP event configuration used in the processing of org.mashupbots.socko.events.HttpEvents.
Minimum number of bytes before content will be compressed if requested by the client. Set to -1 to turn off compression.
List of MIME types of that can be compressed.
Encapsulates the all the data sent in a HTTP request; i.e.
Encapsulates the all the data sent in a HTTP request; i.e. headers and content.
Encapsulates all the data to be sent to the client in an HTTP response; i.e.
Encapsulates all the data to be sent to the client in an HTTP response; i.e. headers and content.
Port of Netty's HttpResponseStatus class for convenience.
HTTP response status code as per RFC 2616.
Details of the HTTP request that initiated the web socket connection or chunk transfer.
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.
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.