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
omcat%206
>
> Filip
>
> -
> To start a new topic, e-mail: users@tomcat.apache.org
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
--
View this message in context:
http://www.nabble.com
send it immediately).
> Could someone please point me to an explanation of this behavior?
>
> Regards,
> felix
> --
> View this message in context:
> http://www.nabble.com/COMET---Delays-in-output-tf4158481.html#a11831204
> Sent from the Tomcat - User mailing list ar
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(
>> ...
> >>
> >> At this point I am experiencing a delay according to the value of the
> >> comet.timeout parameter
> >> before the data is actually arriving at the client (even though flush()
> >> should send it immediately).
> >> Could someone please point me to an explanation of this beh
o an explanation of this behavior?
>>
>> Regards,
>> felix
>
> -------------
> To start a new topic, e-mail: users@tomcat.apache.org
> To unsubscr
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
out parameter
before the data is actually arriving at the client (even though flush()
should send it immediately).
Could someone please point me to an explanation of this behavior?
Regards,
felix
--
View this message in context:
http://www.nabble.com/COMET---Delays-in-output-tf4158481.html#
