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 19286] - httpClient incorrectly closing tunnelled connection right after tunnell established
Date Wed, 30 Apr 2003 15:14:30 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=19286>.
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=19286

httpClient incorrectly closing tunnelled connection right after tunnell established





------- Additional Comments From becke@u.washington.edu  2003-04-30 15:14 -------
Extending HttpConnection sounds reasonable.  My gut reaction is that this will
only be a short term solution though.  In the long term I think it makes sense
to have HttpConnection be an interface and have the ability to add handlers for
various features ala the MethodRetryHandler.  In fact, we could add an isStale
handler now depending on our schedule.

When it comes to extending MultiThreadedHttpConnectionManager (assuming that's
the one you are using) I'm not sure if it's possible at the moment, without a
little tweaking.  Again, I think the long term solution would be to have
pluggable functionality like a HttpConnectionFactory.

Either way, I think we can accomodate the changes you want.  The question is are
we going to do it correctly (add handlers and connection factory, etc.) or are
we going to just relax access to methods/variables.  If we go for option two, I
would suggest that we make the methods/variables deprecated to avoid long term
requirements.

Any thoughts from Oleg, Jeff, Odi?

Mike

Mime
View raw message