FelixG wrote:
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 ca
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() manu
Can you run the comet code-example "chat" success?
I tried many times ,it don't work in tomcat6.0.13
I just try straight the url
http://localhost:8080/examples/jsp/chat/login.jsp
and also modify the server.xml ,change the protocol by "
org.apache.coyote.http11.Http11NioProtocol"
Are there other wo
FelixG wrote:
I'm testing in Eclipse/WinXP locally and on a solaris8 machine over a local
network. The delay
is occuring on both Tomcats.
Ok, locally at least you shouldn't be experiencing any proxy hinder. :-)
The flush should immediately push the data to the client. Did you try
using netca
FelixG wrote:
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(
It seems must send enough bytes of data to client .
try add this code to before you write
for(int j=0;j<500;j++){
writer.println(" ");
}
By the way ,do you try the example of tomcat6.0.13 comet "chat "
when I try to login ,the session always comes error ,it never happen in
tomcat6.0.10
I'm testing in Eclipse/WinXP locally and on a solaris8 machine over a local
network. The delay
is occuring on both Tomcats.
Sebastiaan van Erk wrote:
>
> What kind of environment are you testing in? Does the servlet run on
> your local development machine or over the network. Are there possib
What kind of environment are you testing in? Does the servlet run on
your local development machine or over the network. Are there possibly
transparent proxies between the two endpoints? You could try testing
with network tools such as netcat to debug what's happening.
Regards,
Sebastiaan
Fel
