---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/3334/
---
Review request for shindig.
Summary
---
This is the first of a couple of ga
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/3332/#review4150
---
Ship it!
+1 Sheep it =)
- Henry
On 2011-12-29 20:05:42, Stanton Si
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/3332/
---
Review request for shindig.
Summary
---
The purpose of this patch is to rem
The gadget topics are coded in the gadget xml, developers call the
gadgets.Hub.publish or subscribe function directly. It seems that such
gadget to gadget communication is defined by gadget developer. The use case
I am trying to have is that the end user or the container of the gadgets,
can someho
On Thu, Dec 29, 2011 at 12:23 AM, Wei CSDL Shi wrote:
> Yes, I am looking for how to setup wire between specific gadget instances.
> I've checked the gadget topics, it seems that once gadget A published a
> topic, all the gadget B instances which subscribed to that topic, will be
> invoked. Is th
Yes, I am looking for how to setup wire between specific gadget instances.
I've checked the gadget topics, it seems that once gadget A published a
topic, all the gadget B instances which subscribed to that topic, will be
invoked. Is there a way that I can only invoke one specific gadget B
instance
Did you mean communication between gadgets?
- Henry
On Tue, Dec 27, 2011 at 12:03 AM, Wei CSDL Shi wrote:
>
>
> Section 12 of gadget spec 2.0.1 indicates that the wiring metadata of a
> gadget topic can be used for end user to wire publisher gadgets to
> subscriber gadgets from container level.
