After looking at the TCP packets I can say this:
The use of flush() in COMET *does* push data-packets immediately to the
client, but it seems that
the client (in my case a browser) doesn't recognize/display them until the
outputstream is closed
due to an ERROR/TIMEOUT or until I call close()
Hi,
I'm trying to implement the comet code-example from the Tomcat
documentation,
using Tomcat 6.0.13, Http11NioProtocol is working and my servlet is
implementing CometProcessor.
I am trying to write into the response's PrintWriter with this code in
event():
if (event.getEventType() ==
Hi everyone,
I am trying to get the Adv. IO feature of Tomcat 6.0.13 (running on a sparc
sun solaris 8 with JDK6)
working. After searching the mailing-lists I changed the connector in
server.xml to use the NioProtocol:
Connector port=8080 protocol=org.apache.coyote.http11.Http11NioProtocol
contains
CometProcessor), however if it's included in your webapp then tomcat's
instanceof CometProcessor check fails, causing this error. (If using
mvn, set your dependency scope of the tomcat jars to provided).
Regards,
Sebastiaan
FelixG wrote:
Hi everyone,
I am trying to get the Adv
