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:[EMAIL PROTECTED] 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 [EMAIL PROTECTED] 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
