On Fri, Oct 16, 2009 at 4:41 PM, Ivan Žužak <izu...@gmail.com> wrote:
> Hey Chris, > > 1) The container does load the rpc library. > 2) Each gadget on the container is loaded from a URL that does contain > a rpc token in the fragment part. > 3) I do not see the setRelayUrl and setAuthToken calls. Is this > something that should be automatically generated without my > intervention into shindig code or something that requires changing > shindig? As I understand, these calls should be placed on the > container not in each gadget? > This is something you should add to your container code, ie in the part that generates the gadget iframe's, as a practical example this is how they're generated in Partuza: http://code.google.com/p/partuza/source/browse/trunk/Application/Views/gadget/gadget.php > In any case, does gadget-to-gadget communication go through the > container or directly between two iframes? If I interpret the code > correctly, the setRelayUrl and setAuthToken calls enable communication > between container and gadget, not between two gadgets - when > gadgets.rpc.call is invoked within a gadget and an ID which is not the > container is specified, the wpm transport fails when trying to obtain > the destination frame since window.frames[targetId] is undefined > (since the target is not a child of the gadget, rather it's sibling). > Correct, I thought the RPC calls were container mediated, but I haven't personally looked at that code for a while so I'm hoping that by adding those 2 calls things might magically start to work, and if not you needed those anyhow:)
