API for event driven NIO based on
This API is not specific to HTTP communication.
However, it is minimal in the sense that it defines only
what is required within the scope of HTTP components.
||ConnectingIOReactor represents an I/O reactor capable of establishing
connections to remote hosts.
||Type of I/O event notifications I/O sessions can declare interest in.
||IOEventDispatch interface is used by I/O reactors to notify clients of I/O
events pending for a particular session.
||HttpCore NIO is based on the Reactor pattern as described by Doug Lea.
||Abstract exception handler intended to deal with potentially recoverable
I/O exceptions thrown by an I/O reactor.
||IOSession interface represents a sequence of logically related data exchanges
between two end points.
||ListenerEndpoint interface represents an endpoint used by an I/O reactor
to listen for incoming connection from remote clients.
||ListeningIOReactor represents an I/O reactor capable of listening for
incoming connections on one or several ports.
||SessionBufferStatus interface is intended to query the status of session
||Session input buffer for non-blocking connections.
||Session output buffer for non-blocking connections.
||SessionRequest interface represents a request to establish a new connection
(or session) to a remote host.
||SessionRequestCallback interface can be used to get notifications of
completion of session requests asynchronously without having to wait
for it, blocking the current thread of execution.
||IOReactorStatus represents an internal status of an I/O reactor.