DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=41855>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=41855 ------- Additional Comments From [EMAIL PROTECTED] 2007-03-16 09:11 ------- (please excuse the previous inappropriate insult; the privileged majesties of the kingdom are, unlike the rest of us, under a lot of stress and pressure, and lack time to compose and post better insults). All that to say, your servlet must do 2 things: perform the main work and monitor the connection. This is not the responsibility of the container. Actually the container cannot figure out (not without NIO* at least) that the servlet/socket output was abandoned/closed without attempting to write to it, which would corrupt the response stream content. If your response content can support comment-like data, for example for html comment, or some #ping text, or whatever appropriate to the ongoing protocol, than your servlet could write periodically such comment to check the client connection viability. But such background test, while the main task is still running, requires another thread unless you main task is asynchronous. Depending in the security manager in place, you might not have the right to spawn threads in the servlet container. *NIO: the servletoutputstream isn't a selectable channel, tomcat container would have to perform such monitoring and expose the socket output state in the servlet api, which isn't about to happen soon... -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
