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=14059>.
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=14059

HTP Response does not respond correctly to flush()





------- Additional Comments From [EMAIL PROTECTED]  2002-11-05 16:03 -------
Remy,

In Summary:

There is a difference in behavior of when TC4.0.x and Tc4.1.12 sends the end of 
chunk message for a response.  TC4.0.x sends an end of chunk immediately 
following the stream close() in a servlet response.  TC4.1.12 does not send the 
end of chunk message until the servlet exits its DoPost method.

On the client side, the sun java.net implementation does not return a stream 
from the getInputStream() method until it receives the end of chunk message on 
the wire.  Hence, my "issues".  It looks like the browsers have access to 
intermediate chunks.  Which is why you don't see any issue.

In conclusion,  TC behavior HAS changed;  Is it a bug?  Depends on who you 
ask... I think the behavior change should be at least clearly documented on the 
TC docs if it is NOT determined to be a bug.  However, I do not think the 
close() is being handled correctly.  It is not being handled in the manner it
has been in previous TC releases.

I would like to hear your view on this issue.

Thanks,

-j.p.

--
To unsubscribe, e-mail:   <mailto:tomcat-dev-unsubscribe@;jakarta.apache.org>
For additional commands, e-mail: <mailto:tomcat-dev-help@;jakarta.apache.org>

Reply via email to