users@grizzly.java.net

Re: not sure about this bug

From: Jeanfrancois Arcand <Jeanfrancois.Arcand_at_Sun.COM>
Date: Wed, 19 Nov 2008 13:31:43 -0500

Richard Corsale wrote:
> Oh yeah I mean I see how -1 works , but I didn't know that Cometd worked that way, I just assumed it was always pushing data to a given channel and adding / removing listeners :)
>
> Thanks for the clarification.

Your welcome. I've improved the documentation based on your feedback.
Thanks!

-- Jeanfrancois


> --Richard
>
>
>
>
> ----- Original Message ----
> From: Jeanfrancois Arcand <Jeanfrancois.Arcand_at_Sun.COM>
> To: users_at_grizzly.dev.java.net
> Sent: Wednesday, November 19, 2008 11:54:13 AM
> Subject: Re: not sure about this bug
>
> Salut,
>
> Richard Corsale wrote:
>> Ohhh I see, so its like Cometd , its streaming to a context regardless if anyone is listening or not.
>
> Can you elaborate? With cometd, by default the connection use long polling, e.g. as soon as there is a an event, the connection is resumed. If cometd were using the http-streaming techinique, after an event we would never "resume" the connection.
>
> When setting expirationDelay to -1, it just means that the server will never close the connection if no event happens, and , like you described inside the issue, doesn't detect if the client close the connection (no event are propagated to the CometHandler.onInterrupt()).
>
> Does that help?
>
>> Ok its been reported.
>
> Thanks!!!
>
> -- Jeanfrancois
>
>> --Richard
>>
>>
>>
>>
>>
>>
>> ----- Original Message ----
>> From: Jeanfrancois Arcand <Jeanfrancois.Arcand_at_Sun.COM>
>> To: users_at_grizzly.dev.java.net
>> Sent: Tuesday, November 18, 2008 11:01:03 PM
>> Subject: Re: not sure about this bug
>>
>> Salut,
>>
>> Richard Corsale wrote:
>>> Hi All, while I was working on GF 2. I noticed something strange, but it must have been noted before...
>>>
>>> I have a CometContext in a singleton, If i set the timeout to -1 it never detects dissconnects.
>> yes, that's the expected behavior.
>>
>>
>> so I have set it to 30 Mins and it works as advertisd :). is this a known Bug?
>>
>>
>> It is a documentation bugs. Can you file an issue? I will update the docs and make sure this is properly documented.
>>
>> Thanks!
>>
>> --Jeanfrancois
>>
>>> ----------------------------------------------------------------------
>>> static CometContext cc;
>>> public void addHandler(CometHandler ch){
>>> cc.setExpirationDelay(60000 * 30);
>>> cc.addCometHandler(ch);
>>> }
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe_at_grizzly.dev.java.net
>>> For additional commands, e-mail: users-help_at_grizzly.dev.java.net
>>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe_at_grizzly.dev.java.net
>> For additional commands, e-mail: users-help_at_grizzly.dev.java.net
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe_at_grizzly.dev.java.net
>> For additional commands, e-mail: users-help_at_grizzly.dev.java.net
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_grizzly.dev.java.net
> For additional commands, e-mail: users-help_at_grizzly.dev.java.net
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_grizzly.dev.java.net
> For additional commands, e-mail: users-help_at_grizzly.dev.java.net
>