hc-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ortwin Glück <ortwin.glu...@nose.ch>
Subject Re: connectionManager.releaseConnection()
Date Wed, 30 Mar 2005 12:17:49 GMT

while this completely defeats the purpose of the HTTP keep-alive 
feature, I understand that there are special situations when one needs 
what you describe. That means you can do away with the connection 
pooling altogether. It also means that none of the existing 
ConnectionManager implementatinos suite your needs. You had better 
implementing a completely new ConnectionManager that does not attempt to 
pool a connection but every call to getConnection just creates a new one 
and every call to releaseConnection just closes it. This should be very 
easy to do. Maybe we should provide such a simple non-pooling connection 
manager with the stock version of HttpClient.

Ortwin Glück

Juan Pedro López Sáez wrote:
> Hi Ortwin,
> Actually I'm not experiencing any problem with HttpClient but just want
> to be sure that every connection is really closed and not reused after
> calling method.releaseConnection().
> I'm developing a critical component based on HttpClient to handle lots
> of HTTP connections to different servers and I want it to close every
> HTTP connection.
> Watching some threads I could see that the best way to achieve this
> behaviour is overriding connectionManager.releaseConnection() but I
> don't know how to do it properly.
> Is there any other option to satisfy my needs?
> Thank you very much.
> 	Juan Pedro 

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

View raw message