In your container page, have you initialized each gadget (assuming it's an IFRAME w/ <iframe id="gadget" name="gadget" src=" http://server.com/gadgets/ifr...stuff...#rpctoken=1234"/>) w/: <script> gadgets.rpc.setAuthToken('gadget', '1234'); gadgets.rpc.setRelayUrl('gadget', ' http://server.com/gadgets/files/container/rpc_relay.html'); </script>
? Apropos of some of some recent posts re: rpc.js, the relayUrl bit may not be needed much longer, but depending on your browser/setup it is for now. --John On Mon, May 11, 2009 at 6:25 PM, Jordan Zimmerman <[email protected]> wrote: > >The callback should automatically resolve in the gadget since the > >CALLBACK_NAME'd service is registered by default in rpc.js. Do _any_ > >gadgets.rpc calls work for you? > > They work one-way: from gadget to container. But not the other way. > > -Jordan > > > 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. >
