I see, and what do you usually use for gadget to gadget communication, when they are not in the same container?Implements own service or use another feature from opensocial/shindig?
Thanks Maxwell Sent from my iPhone On 22/12/2010, at 16:51, Henry Saputra <[email protected]> wrote: > inner communication meaning between gadget and container? yes > > - Henry > > On Wed, Dec 22, 2010 at 5:11 AM, Maxwell <[email protected]> wrote: >> I was looking "gadgets.rpc" spec, and looks like this feature also >> just supports "inner communication" is that right? >> >> On Tuesday, December 21, 2010, Maxwell <[email protected]> wrote: >>> So, what do you recommend me to make a "communication" in different >>> containers? Could I use the MessageService? >>> >>> On Tue, Dec 21, 2010 at 5:15 PM, Maxwell <[email protected]> wrote: >>> Nothing specific yet, I'm just writing some tests, and looking if we will >>> be able to use shindig, one of the requirements, it's gadgets talking in >>> different containers, (or browsers). >>> >>> My test will be a simple chat (2 gadgets sending messages), it's easy with >>> pub/sub, i already wrote one, but now we would like to try with different >>> containers. >>> >>> >>> Maxwell >>> >>> On Tue, Dec 21, 2010 at 4:22 PM, John Hjelmstad <[email protected]> wrote: >>> >>> It doesn't -- the "pubsub" feature ferries messages between gadgets by way >>> of the container itself, using in-browser communication. That's true as well >>> of the "pubsub-2" feature as well. Communication btw different gadgets >>> requires a server component, which has typically been built ad hoc. What's >>> your use case? >>> >>> --John >>> >>> On Tue, Dec 21, 2010 at 9:02 AM, Maxwell <[email protected]> wrote: >>> >>>> Does pub/sub provides support to communication between gadgets that are not >>>> in the same container? Maybe another browser window. >>>> >>>> Thanks. >>> >>> >>> >> > > > > -- > Thanks, > Henry
