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

PrinWriter.flush() HttpServletResponse.flushBuffer() do not work

[EMAIL PROTECTED] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|WORKSFORME                  |



------- Additional Comments From [EMAIL PROTECTED]  2001-10-04 03:59 -------
I should clarify that I am implementing a SERVLET-TO-SERVLET streaming 
communication and although the flushing works with a browser it doesn't in
a situation such as shown in my simple example. It could be that the problem
is not with PrinWriter.flush() or HttpServletResponse.flushBuffer(), but with 
another component of Tomcat 4 which is doing some additional buffering behind 
the scenes and thus preventing the output from being sent straight away to the 
client side.
BufferedReader on the client side did not cause any problems on Tomcat 3.
When I run my test example under Tomcat 3.2.3 it outputs banana: yellow, waits 
for 2 seconds then outputs sea: blue, waits for 2 seconds and then outputs 
snow: white before exiting (AS IT SHOULD).
With Tomcat 4 I get all 3 parameters at once and ONLY when the program exits, 
without 
the 2 second wait time between the 3 parameters, showing that flushing the 
writer and the response is not enough to send the output to the client. only 
when the program exits that the output appears.

Reply via email to