hc-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jeffrey Dever <jsde...@sympatico.ca>
Subject Re: Moving from HttpMultiClient to HttpClient
Date Tue, 17 Dec 2002 01:34:15 GMT
All I have at this point is the commit comment:

What's new:

- HostConfiguration, a new class for combining host/proxy info
- HttpConnectionManager, this is a new interface to replace the previous 
- SimpleHttpConnectionManager, an implementation of 
HttpConnectionManager that gives access to a single connection
- When using HttpClient with the multi-threaded connection manager 
HttpConnections must be released before they can be reused. Currently 
there are three ways of doing this:
1) HttpMethod.releaseConnection(), following a client.executeMethod()
2) fully read the method's response stream
3) allow the connection to be garbage collected by losing a reference to 
the method. this is not terribly efficient and is mostly just a safety 
mechanism to ensure that connections are not lost.

What's changed:

- HttpConnectionManager has been renamed to 
MultiThreadedHttpConnectionManager and complies with the 
HttpConnectionManager interface
- HttpClient, most of the previous methods have been deprecated and 
replaced by ones that make sense for multiple thread access. an attempt 
has been made to make all data thread-safe.

dion@multitask.com.au wrote:

>Is there a good summary somewhere of the changes made so that the new 
>HttpClient can be used in place of the old MultiClient?
>I was hoping for something other than a diff/visual scan....
>dIon Gillard, Multitask Consulting
>Blog:      http://www.freeroller.net/page/dion/Weblog
>Work:      http://www.multitask.com.au
>To unsubscribe, e-mail:   <mailto:commons-httpclient-dev-unsubscribe@jakarta.apache.org>
>For additional commands, e-mail: <mailto:commons-httpclient-dev-help@jakarta.apache.org>

View raw message