With the new preference architecture in place timeout settings per connection should not be a problem at all, but still need to HttpParam-enable HttpConnection class. We would also need to able to enumerate connections in the connection pools. Should be double as well I believe.
Oleg -----Original Message----- From: Ortwin Glück [mailto:[EMAIL PROTECTED] Sent: Thursday, September 11, 2003 3:35 PM To: Commons HttpClient Project Subject: Re: MultiThread and setSoTimeout [EMAIL PROTECTED] wrote: > Hi, > > my question is the following: I would like to set different timeouts > between threads..What is the best way to do this? You can wait for the new preference architecture to be finished which shall allow this. > I can't find any methods to set the timeout except in HttpClient and > HttpConnection. Setting it in HttpClient results in the same timeout for > every connection, and, as executing a method causes a connection to be > automatically allocated by the MultiThreadedHttpConnectionManager, I > don't know how to seta timeout for an already allocated HttpConnection. > > A solution could be to use different HttpClients, but this would affect > performances I guess.. Only if you connect to the same host from all threads. Otherwise using a separate Instance of HttpClient for each thread does not affect performance. --------------------------------------------------------------------- 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]
