HTTP message parsers and formatter

- HTTP message parsers and formatter + HTTP message parsers and formatters HttpCore also provides coarse-grained facade type interfaces for parsing and formatting of HTTP messages. Default implementations of those interfaces build upon the Modified: httpcomponents/httpcore/trunk/src/docbkx/nio-ext.xml URL: http://svn.apache.org/viewvc/httpcomponents/httpcore/trunk/src/docbkx/nio-ext.xml?rev=1241149&r1=1241148&r2=1241149&view=diff ============================================================================== --- httpcomponents/httpcore/trunk/src/docbkx/nio-ext.xml (original) +++ httpcomponents/httpcore/trunk/src/docbkx/nio-ext.xml Mon Feb 6 20:15:54 2012 @@ -62,7 +62,7 @@ - efficient memory management: data consumer can read only as much input data as it + efficient memory management: data consumer can read is only as much input data as it can process without having to allocate more memory. @@ -243,7 +243,7 @@ iosession.clearEvent(SelectionKey.OP_REA Quite often I/O sessions need to maintain internal I/O buffers in order to transform input / output data prior to returning it to the consumer or writing it to the underlying channel. Memory management in HttpCore NIO is based on the fundamental - principle that the data consumer can read only as much input data as it can process + principle that the data a consumer can read, is only as much input data as it can process without having to allocate more memory. That means, quite often some input data may remain unread in one of the internal or external session buffers. The I/O reactor can query the status of these session buffers, and make sure the consumer gets notified @@ -453,7 +453,7 @@ ListeningIOReactor ioreactor = new Defau exceptions are usually fatal and will cause the I/O reactor to shut down automatically. - There is a possibility to override this behaviour and prevent I/O reactors from shutting + There is a possibility to override this behavior and prevent I/O reactors from shutting down automatically in case of a runtime exception or an I/O exception in internal classes. This can be accomplished by providing a custom implementation of the IOReactorExceptionHandler interface. @@ -1357,7 +1357,7 @@ HttpAsyncRequestHandler myH

Asynchronous HTTP request consumer - HttpAsyncRequestConsumer facilities the process of + HttpAsyncRequestConsumer facilitates the process of asynchronous processing of HTTP requests. It is a callback interface used by HttpAsyncRequestHandlers to process an incoming HTTP request message and to stream its content from a non-blocking server side @@ -1391,7 +1391,7 @@ HttpAsyncRequestHandler myH has been fully consumed. - This event is invoked only for if the incoming request message has + This event is invoked only if the incoming request message has a content entity enclosed in it. @@ -1454,7 +1454,7 @@ HttpAsyncRequestHandler myH HttpAsyncRequestConsumer implementations are - expected to be tread-safe. + expected to be thread-safe. BasicAsyncRequestConsumer is a very basic implementation @@ -1466,7 +1466,7 @@ HttpAsyncRequestHandler myH

Asynchronous HTTP response producer - HttpAsyncResponseProducer facilities the process of + HttpAsyncResponseProducer facilitates the process of asynchronous generation of HTTP responses. It is a callback interface used by HttpAsyncRequestHandlers to generate an HTTP response message and to stream its content to a non-blocking server side HTTP connection. @@ -1480,7 +1480,7 @@ HttpAsyncRequestHandler myH <methodname>generateResponse</methodname>: - Invoked to generate a HTTP response message head. + Invoked to generate a HTTP response message header. @@ -1532,7 +1532,7 @@ HttpAsyncRequestHandler myH HttpAsyncResponseProducer implementations are - expected to be tread-safe. + expected to be thread-safe. BasicAsyncResponseProducer is a basic implementation @@ -1630,7 +1630,7 @@ HttpResponse response = future.get();

Asynchronous HTTP request producer - HttpAsyncRequestProducer facilities the process of + HttpAsyncRequestProducer facilitates the process of asynchronous generation of HTTP requests. It is a callback interface whose methods get invoked to generate an HTTP request message and to stream message content to a non-blocking client side HTTP connection. @@ -1659,7 +1659,7 @@ HttpResponse response = future.get(); <methodname>generateRequest</methodname>: - Invoked to generate a HTTP request message head. The message is expected + Invoked to generate a HTTP request message header. The message is expected to implement the HttpEntityEnclosingRequest interface if it is to enclose a content entity. @@ -1724,7 +1724,7 @@ HttpResponse response = future.get(); HttpAsyncRequestProducer implementations are - expected to be tread-safe. + expected to be thread-safe. BasicAsyncRequestProducer is a basic implementation @@ -1738,7 +1738,7 @@ HttpResponse response = future.get();

Asynchronous HTTP response consumer - HttpAsyncResponseConsumer facilities the process of + HttpAsyncResponseConsumer facilitates the process of asynchronous processing of HTTP responses. It is a callback interface whose methods get invoked to process an HTTP response message and to stream message content from a non-blocking client side HTTP connection. @@ -1834,7 +1834,7 @@ HttpResponse response = future.get(); HttpAsyncResponseConsumer implementations are - expected to be tread-safe. + expected to be thread-safe. BasicAsyncResponseConsumer is a very basic implementation @@ -2021,7 +2021,7 @@ NHttpClientConnection conn = connfactory check whether the SSL I/O session is ready to accept output data by calling SSLIOSession#isAppOutputReady(), pass control to the protocol handler if it is, and finally call - SSLIOSession#outboundTransport() method in order to do the nessary + SSLIOSession#outboundTransport() method in order to do the necessary SSL handshaking and encrypt application data.