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 29383] - MultiThreadedConnectionManager Accounting Problems
Date Tue, 08 Jun 2004 08:16:27 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=29383>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=29383

MultiThreadedConnectionManager Accounting Problems





------- Additional Comments From olegk@apache.org  2004-06-08 08:16 -------
Mike,

Having HttpConnection#isOpen and HttpConnection#isClosed methods is awfully
confusing. What are reasons for having to call isStale from isOpen? I personally
see no sense in performing stale check in the isOpen method. As a consumer of
that method I do not give a damn whether the connection is stale or not. All I
want to know whether the connection is considered open and whether HttpClient
should attempt to automatically recover in case of connection failure. That's
it. What comfort to me is the fact that the connection is open and valid at the
time I call isOpen when it can still go stale by the time HTTP method executes?

Oleg

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