Convenience implementation of ConnectionHandler which provides implementations for all of the necessary functions.
ClientConnectionHandler is a trait meant to be used with outgoing connections.
This is the base trait for all connection handlers.
A trait encapsulating live information about a connection.
This class is used to report some basic stats about a Connection.
Represent the connection state.
ConnectionVolumeState indicates whether or not if the Server is operating with a normal workload, which is represented by the current ratio of used / available connections being beneath the ServerSettings.
A thin wrapper around a NIO ByteBuffer with data to read
A DataReader is the result of codec's encode operation.
A Delegator is in charge of creating new ConnectionHandler’s for each new connection.
Currently unused; but will eventually be for async delegators, if we decide to allow them
Messages representing why a disconnect occurred.
Subset of DisconnectCause which represent errors which resulted in a disconnect.
A Simple mixin trait that will cause the worker to not automatically unbind this handler if the connection it's attached to is closed.
Simple class which contains parameters for configuring a polling operation
Configuration used to specify a Server's application-level behavior
Mixin containing events just for server connection handlers
A ServerRef is the public interface of a Server.
Contains values for configuring how a Server operates
Represents the current state of a Server.
Represents the startup status of the server.
A Watched handler allows an actor to be tied to a connection.
These are a different class of Commands to which a worker will respond.
Contains the configuration for each Worker.
A WorkerItem is anything that can be bound to worker to receive both events and external messages.
Represents the binding of an item to a worker
This keeps track of all the bound worker items, and properly handles added/removing them
This is a Worker's public interface.
This is passed to handlers to give them a way to synchronously write to the connection.
Servers can be thought of as applications, as they provide Delegators and ConnectionHandlers which contain application logic.
Like the server actor, it is critical that instances of this actor get their own thread, since they block when waiting for events.