Note re: IFPC that it is for many users of gadgets.rpc being deprecated. That's because it bears a higher burden for installation -- the container needs to actively install a relay file and initialize it precisely.
None of the other transports require this. RMR *should* work for all browsers as well, though I can't remember if there are outliers. --John On Wed, Mar 17, 2010 at 8:41 AM, Ivan Žužak <[email protected]> wrote: > Hi Zhenhua, > > No, we haven't modified the other source files responsible for other > types of transports since or project assumes HTML5 cross-document > messaging APIs are available. I think getting IFPC working would be > enough since it works in most (all?) browsers. And I'm guessing that > either 1) it works already without any changes or 2) it shouldn't be > much trouble to do. > > Cheers, > Ivan > > On Wed, Mar 17, 2010 at 05:00, Zhenhua Guo <[email protected]> wrote: > > Thank you very much. > > I was trying to modify those files to fit our needs. You save me lots of > time. > > One problem is if wmp (it's a new feature in HTML5 I believe) is not > > supported, other mechanisms need to be used such as hidden frame, > > frameElement. Have you modified fe.transport.js, ifpc.transport.js, > > etc as well? > > > > Gerald > > > > On Tue, Mar 16, 2010 at 4:44 PM, Ivan Žužak <[email protected]> wrote: > >> Here are the two files containing changes we made to make direct > >> inter-gadget communication work (you can do a diff to see the exact > >> changes made, there's only a few): > >> > >> http://dl.dropbox.com/u/1559679/rpc.js > >> http://dl.dropbox.com/u/1559679/wpm.transport.js > >> > >> With these changes we use gadgets.rpc.call to do RPC calls between > >> gadgets without container mediation, as John described in the > >> discussion I linked before. RPC is a different communication mechanism > >> than PUBSUB so it may not fit every need, but it's better than > >> nothing. See the rpc.js inline comments of the call method for a > >> description of how to invoke it. Unfortunately, the demo version of > >> our project is offline, so I'll link to it when it gets back online. > >> > >> Hope this helps, > >> Ivan > >> > >> On Tue, Mar 16, 2010 at 20:09, Cesar William <[email protected]> > wrote: > >>> I'm interested too. > >>> > >>> On Tue, Mar 16, 2010 at 3:57 PM, Ivan Žužak <[email protected]> wrote: > >>> > >>>> We're using a slightly modified gadgets.rpc feature for direct > >>>> inter-gadget communication in our project. Check this thread out for > >>>> some pointers and issues http://markmail.org/thread/st6amwanlmarsqov. > >>>> Let me know if you're interested and I can e-mail you the modified > >>>> files. > >>>> > >>>> Cheers, > >>>> Ivan > >>>> > >>>> On Tue, Mar 16, 2010 at 18:39, Jon Maul <[email protected]> wrote: > >>>> > I'm pretty sure e means > >>>> > > >>>> > http://code.google.com/apis/opensocial/docs/0.8/reference/gadgets/#gadgets.pubsub > >>>> > > >>>> > I've yet to encounter a working example, however. > >>>> > > >>>> > -Jon > >>>> > > >>>> > On 3/16/2010 1:31 PM, Zhenhua Guo wrote: > >>>> >> > >>>> >> You mean this > http://code.google.com/apis/gadgets/docs/pubsub.html ? > >>>> >> The APIs are deprecated and unsupported officially now. > >>>> >> > >>>> >> Gerald > >>>> >> > >>>> >> On Tue, Mar 16, 2010 at 1:21 PM, Jon Maul<[email protected]> wrote: > >>>> >> > >>>> >>> > >>>> >>> Is there a container that supports it? The classic example of one > >>>> gadget > >>>> >>> publishing random numbers to the other doesn't seem to work on > wso2 nor > >>>> >>> iGoogle. > >>>> >>> > >>>> >>> Also: > http://www.mail-archive.com/[email protected]/msg00021.html > >>>> >>> > >>>> >>> -Jon > >>>> >>> > >>>> >>> On 3/16/2010 1:07 PM, Cesar William wrote: > >>>> >>> > >>>> >>>> > >>>> >>>> Yes, the pubsub feature. > >>>> >>>> > >>>> >>>> On Tue, Mar 16, 2010 at 1:57 PM, Zhenhua Guo<[email protected]> > >>>> wrote: > >>>> >>>> > >>>> >>>> > >>>> >>>> > >>>> >>>>> > >>>> >>>>> Is there any support for inter-gadget communication in shindig > impl? > >>>> >>>>> > >>>> >>>>> Gerald > >>>> >>>>> > >>>> >>>>> > >>>> >>>>> > >>>> >>> > >>>> >>> > >>>> > > >>>> > >>> > >> > > >
