Hi and thank you for all the help.
My response is embedded below.
--Zaid
http://altmobile.com
On Jan 16, 2008, at 11:46 AM, Jeanfrancois Arcand wrote:
>
>
> ALT Mobile DEV wrote:
>> as expected... perfect :-)
>
> Thanks
>
>> Do you have a Bayeux Comet example with Grizzlets?
>
> Since cometd is a client side technology, you don't need to write
> any Grizzlet as by default, a cometd client will work with any web
> server that support the bayeux protocol (JSON based). Take a look at
> the following blog for a client examples
>
> http://weblogs.java.net/blog/jfarcand/archive/2007/11/finally_grizzly.html
>
> the way it works is the DOJO client is sending http request, and the
> request body take the form of a JSON message. On the server side,
> Grizzly Cometd implementation receive the request, decode the JSON
> message and execute the proper operation. Like I've said, any web
> server that understand bayeux will be able to decode the message.
[ZAID] yes, I used the blog as a reference for our current Grizzlet
implementation but it was not obvious to me how is the channel/
operation exposed to the Grizzlet:
[72] String action = req.getParameterValues("action")[0];
[73] String name = req.getParameterValues("name")[0];
Our current implementation of the Dynamic Mashup Server runs 1 mash-up
on each Grizzly server which is connected to the Web 2.0 containers.
That architecture works well for consumer mash-ups. An alternative use
case is found in enterprise dashboard-style mash-ups where the AJAX
browser client wants to display multiple mash-ups on the same page.
For example, a GlassFish dashboard could display the compilation
status/bug list of each GlassFish component. So that's 10+ mash-ups
where each mash-up aggregates 2 remote HTTP calls: 1 for the bug list
and another for the continues integration stuff.
If a Cometd/Bayeux client can request multiple channels/operations to
the server (port, Grizzly server, Grizzlet, Web 2.0 container) then
that's the bees knees since we can selectively update specific aspects
of this meta mash-up client.
>
>
> Now you might want to have client that aren't supporting bayeux
> (they *don't* encode the request body using JSON) to be able to
> interact with the cometd 'channel' (be able to update bayeux
> clients). To do that, you can use Grizzly Comet or Grizzlet to get
> notification (or to push) data to those client. Before I go into the
> details, are you planning to use Comet *and* Cometd client (and do
> they have to interact each other via Grizzy Comet or Cometd)?
>
[ZAID] yes, with your help :-)
> If yes, get ready to get a long email explaining how to do it :-) :-)
>
> A+
>
> -- Jeanfrancois
>
>
>> continued thanks.
>> --Zaid
>> http://altmobile.com
>> On Jan 15, 2008, at 10:16 PM, Jeanfrancois Arcand wrote:
>>>
>>>
>>> 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:
>>>
>>> Should have read:
>>>
>>> > Yes :-( I didn't expected that GrizzLET will be used like you just
>>> > explained. Mainly, since GrizzLET build on top of Grizzly Comet,
>>> the
>>> > CometHandler I did for GrizzLET is registered as '/comet'. Since
>>> there is
>>> > only one CometEngine (this is a singleton), all Grizzlets will
>>> be invoked
>>> > when the Grizzly Comet do a push, as internally it will do:
>>>
>>> Its Grizzlet that build on top of Grizzly Comet, nor Grizzly :-)
>>>
>>> A+
>>>
>>> --jeanfrancois
>>>
>>>
>>>
>>>> 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
>>>
>> ---------------------------------------------------------------------
>> 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
>