Home » HttpComponents-Core-4.0.1 » org.apache.http.impl » [javadoc | source]
org.apache.http.impl
public class: DefaultHttpServerConnection [javadoc | source]
java.lang.Object
   org.apache.http.impl.AbstractHttpServerConnection
      org.apache.http.impl.SocketHttpServerConnection
         org.apache.http.impl.DefaultHttpServerConnection

All Implemented Interfaces:
    HttpInetConnection, HttpServerConnection

Default implementation of a server-side HTTP connection.
Constructor:
 public DefaultHttpServerConnection() 
Method from org.apache.http.impl.DefaultHttpServerConnection Summary:
bind,   toString
Methods from org.apache.http.impl.SocketHttpServerConnection:
assertNotOpen,   assertOpen,   bind,   close,   createHttpDataReceiver,   createHttpDataTransmitter,   createSessionInputBuffer,   createSessionOutputBuffer,   getLocalAddress,   getLocalPort,   getRemoteAddress,   getRemotePort,   getSocket,   getSocketTimeout,   isOpen,   setSocketTimeout,   shutdown
Methods from org.apache.http.impl.AbstractHttpServerConnection:
assertOpen,   createEntityDeserializer,   createEntitySerializer,   createHttpRequestFactory,   createRequestParser,   createResponseWriter,   doFlush,   flush,   getMetrics,   init,   isEof,   isStale,   receiveRequestEntity,   receiveRequestHeader,   sendResponseEntity,   sendResponseHeader
Methods from java.lang.Object:
clone,   equals,   finalize,   getClass,   hashCode,   notify,   notifyAll,   toString,   wait,   wait,   wait
Method from org.apache.http.impl.DefaultHttpServerConnection Detail:
 public  void bind(Socket socket,
    HttpParams params) throws IOException 
    {@inheritDoc}

    CoreConnectionPNames#TCP_NODELAY parameter determines whether Nagle's algorithm is to be used. The Nagle's algorithm tries to conserve bandwidth by minimizing the number of segments that are sent. When applications wish to decrease network latency and increase performance, they can disable Nagle's algorithm (that is enable TCP_NODELAY). Data will be sent earlier, at the cost of an increase in bandwidth consumption.

    CoreConnectionPNames#SO_TIMEOUT parameter defines the socket timeout in milliseconds, which is the timeout for waiting for data. A timeout value of zero is interpreted as an infinite timeout.

    CoreConnectionPNames#SO_LINGER parameter defines linger time in seconds. The maximum timeout value is platform specific. Value 0 implies that the option is disabled. Value -1 implies that the JRE default is to be used. The setting only affects socket close.

 public String toString()