Salut,
ALT Mobile DEV wrote:
> thanks for the quick responses.
>
> Will this also support non-cometd Grizzlets where the client does _not_
> specify a comet path.
Yes it will.
>
> In our Dynamic Mashup Server, we want to allow the client to specify the
> behavior of the server through URL parameters.
>
> So an AJAX client will use a URL such as http://altmobile.com:xxx
>
> and a long-polling Comet client will use a URL such as
> http://altmobile.com:xxx?use-comet&refresh-increment=5
>
> and a Bayeux Comet client will use a predefined Comet context path such
> as the URL http://altmobile.com:xxx/comet?use-comet&refresh-increment=5
OK let me ask a couple of questions. Here you seems to use two concepts:
(1) Comet: Some Ajax clients send http request and the body (the
message) is based on some custom protocol/messages.
(2) Cometd/Bayeux: Some Ajax clients send http message and the body (the
message) is written using Bayeux (JSON).
This is quite interesting If I understand properly :-)
>
>
> That's our plan for Grizzly. Do you think that this is doable with the
> Grizzlet architecture?
Yes it will, but you gonna need to bootstrap/embed the grizzly-cometd
module AND the Grizzlet (like you already did). Now when you listen to a
port (let say 3434), can that port receive both comet and cometd
requests? Currently a port support comet *or* cometd, but not both (this
is quite simple to implement btw).
Thanks
-- Jeanfrancois
>
> thanks.
>
> --Zaid
>
> http://altmobile.com
>
>
>
> On Jan 15, 2008, at 10:11 PM, Jeanfrancois Arcand wrote:
>
>> Hi,
>>
>> ALT Mobile DEV wrote:
>>> Hi,
>>> I'm running multiple servers in the same JVM where each server is
>>> associated with a different instance of the same Grizllet class. Each
>>> server of course is bound to a different port.
>>> Confusingly, the unique content from each Grizzlet is pushed to all
>>> clients irrespective of the server:port they are connected.
>>
>> Yes :-( I didn't expected that Grizzly will be used like you just
>> explained. Mainly, since Grizzly build on top of Grizzly Comet, the
>> CometHandler I did for Grizzly is registered as '/comet'. Since there
>> is only one CometEngine (this is a singleton), all Grizzlet will be
>> invoked when the Grizzly Comet do a push, as internally it will do:
>>
>> cometContext.notify(...);
>>
>> and the cometContext is bind to 'comet'.
>>
>>> It seems that the AsyncConnection is shared across all Grizzlets and
>>> servers.
>>> I was expecting that:
>>> Grizzly server = unique port + unique Grizzlet instance + unique
>>> comet context.
>>
>> OK I've just added a new API to let you customize the
>> cometContextName. When you initialize the GrizzlyAdapter, just pass
>> the name of the cometContext you want to use. In your case, it can be
>> the just the port like the following:
>>
>>> 113 AsyncHandler asyncHandler = new DefaultAsyncHandler();
>>> 114 asyncHandler.addAsyncFilter(new CometAsyncFilter());
>>> 115 selectorThread.setAsyncHandler(asyncHandler);
>>> 116 117 118 GrizzletAdapter adapter = new
>>> GrizzletAdapter(String.valueOf(port));
>>> 119 selectorThread.setAdapter(adapter);
>>> 120 Grizzlet grizzlet =
>>> (Grizzlet)loadInstance(grizzletClassName);
>>> 121
>>
>> Try it and let me know if that works :-) I've uploaded the new
>> artifacts to the m2 repository, or you can rebuild the comet module to
>> get the changes.
>>
>> Thanks
>>
>> -- Jeanfrancois
>>
>>
>>
>>> thanks for any help.
>>> --Zaid
>>> http://altmobile.com
>>> ---------------------------------------------------------------------
>>> 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
>