Interface Server
- All Known Implementing Classes:
ContainerServer
,ProcessorServer
Server
interface represents a handler that is
used to process Socket
objects. Implementations of
this object will read HTTP requests for the provided sockets and
dispatch the requests for processing by the core protocol handler.
The intended use of a Server
is that it be used in
conjunction with a Container
object, which acts as the
primary protocol handler for a server. Typically the server will
deliver callbacks to a container with both Request
and
Response
objects encapsulating the transaction.
Core responsibilities of the server are to manage connections, to ensure that all HTTP requests are collected, and to dispatch the collected requests to an appropriate handler. It is also required to manage multiplexing such that many connections can be processed concurrently without a high latency period.
- Author:
- Niall Gallagher
-
Method Summary
-
Method Details
-
process
Used to process theSocket
which is a full duplex communication link that may contain several HTTP requests. This will be used to read the requests from theSocket
and to pass these requests to aContainer
for processing.Typical usage of this method is to accept multiple sockets objects, each representing a unique HTTP channel to the client, and process requests from those sockets concurrently.
- Parameters:
socket
- this is the connected HTTP socket to process- Throws:
IOException
-
stop
This method is used to stop theServer
such that it will accept no more sockets. Stopping the server ensures that all resources occupied will be released. This is required so that all threads are stopped, and all memory is released.Typically this method is called once all connections to the server have been stopped. As a final act of shutting down the entire server all threads must be stopped, this allows collection of unused memory and the closing of file and socket resources.
- Throws:
IOException
-