commons-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Oleg Kalnichevski <ol...@apache.org>
Subject Re: HttpClient : using SSL connection pool (or session pool)
Date Tue, 30 Aug 2005 21:51:45 GMT
On Tue, 2005-08-30 at 14:45 -0700, sol myr wrote:
> Hi,
> 
> I intend to use the commons "HttpClient" for SSL communication .
> For performace, I'd like to have a socket pool (in more detail : the server to 
> which I'm connecting is customized, its code is under my control.  Now when 
> my client starts up it should open a pool of, say,  100 sockets, do SSL 
> verification & key negotiation, and from now on all those connections 
> will be "kept alive", and used as necessary ).
>  
> Does HttpClient support this, and if so - could anyone please point me 
> to a code example on the web, or at least mention the name of the 
> classes involved ?

Yes, it does. HttpClient per default reuses connections that can be kept
alive. For more details refer to:

HttpClient multi-threading guide:
http://jakarta.apache.org/commons/httpclient/threading.html

HttpClient optimization guide:
http://jakarta.apache.org/commons/httpclient/performance.html#Connection
%20persistence

HttpClient SSL guide:
http://jakarta.apache.org/commons/httpclient/sslguide.html#Known%
20limitations%20and%20problems

Hope this helps

Oleg

>  
> Thanks very much
> 
> 
> 		
> ---------------------------------
>  Start your day with Yahoo! - make it your home page 


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


Mime
View raw message