hc-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From httpclient-...@jakarta.apache.org
Subject [Jakarta-HttpClient Wiki] Updated: HttpClientApiRedesign
Date Sun, 16 Jan 2005 21:06:23 GMT
   Date: 2005-01-16T13:06:23
   Editor: RolandWeber
   Wiki: Jakarta-HttpClient Wiki
   Page: HttpClientApiRedesign
   URL: http://wiki.apache.org/jakarta-httpclient/HttpClientApiRedesign

   no comment

Change Log:

------------------------------------------------------------------------------
@@ -182,17 +182,11 @@
 
 provides
 
- * asynchronous execution interface for HTTP requests. Responses and errors are reported
as callbacks. Implementations will require an {{{ HttpConnection }}} for communication. It
is their responsibility to get it somehow.
+ * asynchronous execution interface for HTTP requests. Responses and errors are reported
as callbacks. Implementations will require an {{{ HttpClientConnection }}} for communication.
It is their responsibility to get it somehow.
 
    a. {{{ HttpAsyncLink }}} interface for sending requests asynchronously
    a. {{{ HttpAsyncCallback }}} interface
 
- * minimal implementation of the asynchronous execution interface.
-
-   a. {{{ SimpleAsyncLink }}} class implementing {{{ HttpAsyncLink }}}
-
- The minimal implementation spawns a new thread that sends the request over a connection
and waits for a response. The callback interface is invoked by that thread. The connection
is passed to the constructor. The minimal implementation handles at most one request at a
time and therefore does not have to maintain a request queue. It can be used by applications
that want to use a single connection asynchronously and handle synchronization themselves.
-
  * result lookup interface for HTTP responses.
 
    a. {{{ HttpAsyncResult }}} interface for checking whether the response is available, and
getting it
@@ -202,10 +196,16 @@
 
    a. {{{ StdAsyncCallbackHandler }}} class implementing {{{ HttpAsyncCallback }}}, {{{ HttpAsyncResult
}}}, {{{ HttpAsyncNotify }}}
 
+ * minimal implementation of the asynchronous execution interface.
+
+   a. {{{ SimpleAsyncLink }}} class implementing {{{ HttpAsyncLink }}}
+
+ The minimal implementation spawns a new thread that sends the request over a connection
and waits for a response. The callback interface is invoked by that thread. The connection
is passed to the constructor. The minimal implementation handles at most one request at a
time and therefore does not have to maintain a request queue. It can be used by applications
that want to use a single connection asynchronously and handle synchronization themselves.
+
  * standard implementation of the asynchronous execution interface.
 
    a. {{{ StdAsyncLink }}} class implementing {{{ HttpAsyncLink }}}
- The standard implementation spawns a new thread that alternately sends requests over a connection
and waits for a response. Unlike {{{ SimpleAsyncLink}}}, it maintains a queue of requests
to be processed. It can be used by multiple threads simultaneously. It supports persistent
use of a connection, but not pipelining. The constructor gets either a connection, or a connection
manager.
+ The standard implementation spawns a new thread that alternately sends requests over a client
connection and waits for a response. Unlike {{{ SimpleAsyncLink}}}, it maintains a queue of
requests to be processed. It can be used by multiple threads simultaneously. It supports persistent
use of a connection, but not pipelining. The constructor gets either a client connection,
or a connection manager.
 
  * pipelining implementation of the asynchronous execution interface. See note on Pipelining
below.
 

---------------------------------------------------------------------
To unsubscribe, e-mail: httpclient-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: httpclient-dev-help@jakarta.apache.org


Mime
View raw message