Full Streaming vs Early Closing in Comet

[hyongil]

I am currently using DWR 2.0.4 and looking at Active Reverse Ajax support using DWR.

According to documentation, DWR2.0.4 and onwards, early closing mode is default, and does not require "maxWaitAfterWrite" parameter. and I believe the default value of this parameter is -1 which is same as in Full Streaming mode. if this is the case, how can I differenciate enabling Full Streaming mode verse Early closing mode.

When I add the following parameter to web.xml and monitor through firebug from firefox, I noticed that the same connection is reconnected every 60 seconds.

<init-param>
  <param-name>maxWaitAfterWrite</param-name>
  <param-value>-1</param-value>
</init-param>

However when I change to the value from -1 to 5000, it looks like new connection is created for that client every 5 seconds.  Can someone tell me when I should choose one over the other?

Any help will be greatly appreciated.
Thanks,

[Joe Walker-3]

On Wed, Jun 25, 2008 at 8:32 PM, hyongil <hyong.moon@...> wrote:

I am currently using DWR 2.0.4 and looking at Active Reverse Ajax support
using DWR.

According to documentation, DWR2.0.4 and onwards, early closing mode is
default, and does not require "maxWaitAfterWrite" parameter. and I believe
the default value of this parameter is -1 which is same as in Full Streaming
mode. if this is the case, how can I differenciate enabling Full Streaming
mode verse Early closing mode.

The default is 500 - i.e. wait for half a second after output before forcing all the buffers to flush by closing and reconnecting.
 

When I add the following parameter to web.xml and monitor through firebug
from firefox, I noticed that the same connection is reconnected every 60
seconds.

<init-param>
 <param-name>maxWaitAfterWrite</param-name>
 <param-value>-1</param-value>
</init-param>

However when I change to the value from -1 to 5000, it looks like new
connection is created for that client every 5 seconds.  Can someone tell me
when I should choose one over the other?

Unless you are sending large slow block of data, there isn't much point in waiting for 5 seconds after output before flushing. Either you know streaming works (use -1) or you're not sure (use 500, or less if you're server is fast and lightly loaded).

Joe.