A better container approach would probably be a straight XHR to some sort of RPC service that provides meta data (and avoid any iframe communication entirely). This is a valid approach, certainly, but I'm not quite convinced that it's worth doing it this way vs. using the shindig core libraries directly to get at that data at render time. I assume that very few sites actually have static html as their parent pages. It would not be a very efficient way to do this.
~Kevin On Jan 18, 2008 7:03 AM, Martin Webb <[EMAIL PROTECTED]> wrote: > On 16/01/2008, Kevin Brown <[EMAIL PROTECTED]> wrote: > > > > ModulePrefs are already exposed in the Gadget / GadgetSpec object. We > > expect > > that most containers will use this library directly to get access to > this > > meta data. Doing all of this in javascript is extraordinarily > cumbersome, > > and in the long run probably isn't necessary. We could certainly > implement > > this in pure JS, but I don't think that will be practical for real > > implementations due to the cost of iframe->container communication. > > > I was think more along the lines of doing a container->iframe to go get > the > GadgetSpec. Is this just as expensive? > > Martin >
