tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 6160] - HttpServletResponse.flushBuffer() fails to flush data to client
Date Fri, 01 Feb 2002 16:27:03 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=6160>.
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=6160

HttpServletResponse.flushBuffer() fails to flush data to client

remm@apache.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |WONTFIX



------- Additional Comments From remm@apache.org  2002-02-01 16:27 -------
That's strange, but I'm against adding workarounds for obvious JDK bugs. It must
be dealing with some buffering issues or something like that, and is extremely
risky to fix for a very narrow use case. So it won't be fixed in the current
connector (so I mark the bug as WONTFIX).

I don't know yet if the new HTTP connector will fix it, but it will be written
primarily for HTTP spec compliance, robustness and speed, not to work around JDK
bugs. It will also have a much cleaner design, which separates the buffering
from the connector itself. This may fix the problems (at least on the server side).

I find it extremely strange that the JDK version on the server side would also
affect the result.

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


Mime
View raw message