Great, well then I'll start testing 3.0 alpha within our application.
thanks! Mark
Oleg Kalnichevski wrote:
Mark,
This is not that much of a problem as HttpClient always resets socket timeout on the active connection prior to executing a method. The problem is socket timeout setting is simply not thread safe. Socket timeout value may change while connection is still being initialized leading to unpredictable results.
This is a known limitation of 2.0 API which has already been solved in CVS HEAD. 3.0 API (currently at alpha1) allows socket timeout to be set at the HttpMethod level
http://issues.apache.org/bugzilla/show_bug.cgi?id=24154
Oleg
-Mark
______________________________________________________________________ --------------------------------------------------------------------- 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]
-- Mark Diggory Software Developer Harvard MIT Data Center http://www.hmdc.harvard.edu
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
