On Wed, Apr 8, 2009 at 10:52 AM, Jordan Zimmerman <[email protected]> wrote:
> The spec is very thin on what the signature of the handler is: > http://code.google.com/apis/opensocial/docs/0.7/reference/gadgets.rpc.ht > ml#register<http://code.google.com/apis/opensocial/docs/0.7/reference/gadgets.rpc.ht%0Aml#register> > > I look into the code and it appears that "this.f" refers to the iframe > window's name. Why the name? Wouldn't the iframe's ID be better? Also, > why not include the module ID or the application ID? The iframe ID is not accessible by the iframe itself. We don't bother with other ids because the container can easily map these on their own, and the size of the container -> gadget payload must be kept as small as possible (hence the cryptic property names). > > > I'd be happy to make these changes if you like. > > Jordan Zimmerman > Principal Software Architect > 831.647.4712 > 831.214.2990 (cell) > [email protected] > > SHOP*COMTM > Shop Smart, Save Big(tm) > www.shop.com > > > -----Original Message----- > From: Kevin Brown [mailto:[email protected]] > Sent: Wednesday, April 08, 2009 10:24 AM > To: [email protected] > Subject: Re: > http://cwiki.apache.org/SHINDIGxSITE/how-to-support-features-that-depend > -on-gadgetsrpc.html<http://cwiki.apache.org/SHINDIGxSITE/how-to-support-features-that-depend%0A-on-gadgetsrpc.html> > > See documentation on the 'process' function in the source ( > http://svn.apache.org/viewvc/incubator/shindig/trunk/features/src/main/j > avascript/features/rpc/rpc.js?revision=762984&view=markup<http://svn.apache.org/viewvc/incubator/shindig/trunk/features/src/main/j%0Aavascript/features/rpc/rpc.js?revision=762984&view=markup> > ) > > This should probably be moved to register to more closely match the > calling > API I suppose. > > On Wed, Apr 8, 2009 at 10:13 AM, Jordan Zimmerman <[email protected]> > wrote: > > > *bump* > > > > What are the values passed to the handler? How can I get the iframe ID > > or any value that allows resolution to the iframe that posted the > > message? > > > > Jordan Zimmerman > > Principal Software Architect > > 831.647.4712 > > 831.214.2990 (cell) > > [email protected] > > > > SHOP*COMTM > > Shop Smart, Save Big(tm) > > www.shop.com > > > > > > -----Original Message----- > > From: Jordan Zimmerman [mailto:[email protected]] > > Sent: Monday, April 06, 2009 5:11 PM > > To: [email protected] > > Subject: RE: > > > http://cwiki.apache.org/SHINDIGxSITE/how-to-support-features-that-depend > > > -on-gadgetsrpc.html<http://cwiki.apache.org/SHINDIGxSITE/how-to-support- > features-that-depend%0A-on-gadgetsrpc.html<http://cwiki.apache.org/SHINDIGxSITE/how-to-support-%0Afeatures-that-depend%0A-on-gadgetsrpc.html> > > > > > > How does the handler passed to gadgets.rpc.register() get context for > > the gadget? i.e. how does it know which gadget on the page is the > > caller? It seems there is a structure passed that has a few fields, > but > > none of them correspond to anything I'm familiar with. Getting the > > application ID or module ID would be nice. > > > This message (including any attachments) is intended only for > the use of the individual or entity to which it is addressed and > may contain information that is non-public, proprietary, > privileged, confidential, and exempt from disclosure under > applicable law or may constitute as attorney work product. > If you are not the intended recipient, you are hereby notified > that any use, dissemination, distribution, or copying of this > communication is strictly prohibited. If you have received this > communication in error, notify us immediately by telephone and > (i) destroy this message if a facsimile or (ii) delete this > message > immediately if this is an electronic communication. > > Thank you. >
