hc-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Eric Johnson <e...@tibco.com>
Subject Re: DO NOT REPLY [Bug 21329] - Add InputStream buffering.
Date Thu, 02 Sep 2004 19:55:54 GMT
I thought about this as well this morning, and couldn't figure out any 
flaws with the patch.


Oleg Kalnichevski wrote:

>I have been also thinking about repercussions on the reliability of the
>stale connection check. I tend to conclude that with the existing
>architecture (no HTTP pipelining support + response 'garbage' check)
>there is virtually no chance of reading past the response body.
>HttpClient always makes sure that 
>(1) a new request can be executed over the same connection only after
>the previous response has been consumed in its entirety
>(2) drops the connection whenever it detects illegal content past the
>declared response body 
>Am I missing something?
>On Thu, 2004-09-02 at 14:23, Michael Becke wrote:
>>Hi Roland,
>>Yes, that was definitely part of the discussion, and this seems to be a 
>>pretty good solution for that.  Now that I've slept on it , I think 
>>this also came up when were originally discussing isStale() and how to 
>>determine if a connection is still valid.  Does buffering at this level 
>>cause problems here?  My gut reaction is that is that is could, but 
>>probably won't under most conditions.  My feeling is that there 
>>shouldn't be anything buffered between requests.  Does anyone have a 
>>good real-world test case for this?

To unsubscribe, e-mail: commons-httpclient-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-httpclient-dev-help@jakarta.apache.org

View raw message