Hi there, I'm trying to test out Tomcat's comet support by building a test application to exploit this feature. What I am doing is to let the connection continue to stay open by not calling event.close() on neither a BEGIN/READ event. Despite setting the event.setTimeout(-1) on BEGIN event, eventually I receive an ERROR state and this forces me to call event.close() which effectively turns off comet. The only way that I can prolong the inevitable timeout is by having a background thread that runs every 5 seconds to write something to the connection's response. Do I have to do such a thing? Can I not enable an option to let the connection stay open indefinitely?
Thanks in advance. -- View this message in context: http://www.nabble.com/Comet-error-state-always-happen--why--tp24007062p24007062.html Sent from the Tomcat - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
