On Thu, Dec 3, 2009 at 6:55 AM, jss9920 <jss9...@gmail.com> wrote: > I would like to start rendering my gadgets on unique locked domains but am > getting a bit confused about where to start... > > Since the container generates the gadget iframe urls, it would seem that > implementing locked domain would be a container side affair, but I see > configuration options for locked domain support in the shindig container.js > file and I also see associated Java classes that do a lot of locked domain > work in the Shindig codebase (Java Shindig 1.0 release)... > > So is there actually work that needs to be done on both the container side > and the Shindig side to enable locked domain gadgets? >
Yes. Shindig can only enforce the locked domain, but the container still needs to generate it. The JSON RPC handler for gadget metadata can provide rendering urls, or, alternatively, the container could directly use UrlGenerator to get the appropriate gadget rendering url. > > Any pointers on how to get started (even high level) would be helpful and > much appreciated. > > Thanks! >
