hc-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kalnichevski, Oleg" <oleg.kalnichev...@bearingpoint.com>
Subject RE: SoTimeout setting
Date Mon, 27 Oct 2003 15:53:10 GMT
Odi,
I agree it may pose some threading problems. But we should make a reasonable effort at trying
to solve it, as the capability to enumerate HTTP connections would also be required to tackle
the following bug as well:

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16124

Oleg

-----Original Message-----
From: Ortwin Gl├╝ck [mailto:ortwin.glueck@nose.ch]
Sent: Monday, October 27, 2003 16:26
To: Commons HttpClient Project
Subject: Re: SoTimeout setting


Maybe you can write your own / tweak existing connection manager in a 
clever way. Maybe it's worth thinking about that for some time.

Oleg: I remember now. Still this would probably introduce subtle 
threading problems. I am not sure how you want to address that...

HTH

Odi

linea@libero.it wrote:

> My scenario is the following:
> I am trying to share the same client between different threads,
> each of them should execute an http method to an url, possibly the same 
> url.
> If a timeout occurs for any one of the executeMethod() calls 
> asynchronously executed by the different threads, I would like to let 
> the thread retry the method with a longer timeout. If I can't modify the 
> timeout for any connections in the pool, how can I get a connection with 
> a different timeout just for that thread and not for all of them?
> 
> thanks


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


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


Mime
View raw message