hc-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 26500] - New socket timeout value wont have effect if connection is reused
Date Wed, 04 Feb 2004 02:31:20 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=26500>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

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

New socket timeout value wont have effect if connection is reused

becke@u.washington.edu changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Target Milestone|2.0 Final                   |2.1 Final



------- Additional Comments From becke@u.washington.edu  2004-02-04 02:31 -------
Patch applied to 2.0.  

This problem is a little more difficult in HEAD.  The socket timeout is set in HttpConnection.open()
and 
setSoTimeout() is deprecated.  Any preference on how we should handle this?  Here are a few
quick 
ideas that come to mind:

 - un-deprecate setSoTimeout()
 - add a method for synchronizing an HttpConnection with its params
 - remove support for changing a connection once opened
 - something else...

Mike

---------------------------------------------------------------------
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