Additionally, a container and a domain can be related in different ways. A container is more of a configuration distinction than anything.
You might have two containers on a single production system that used the same domain. You might have multiple domains returned from the same container depending on the context of how it was used. How containers map to domains is essentially up to you, as an implementor, though the default implementation allows you to specify it in the config file, which is probably the most basic mapping there is. On Mon, Dec 15, 2008 at 12:35 PM, Brian Eaton <[email protected]> wrote: > container=shindig is not authenticated in any way. It's a hint about > the container, but don't trust it for choosing whether to serve > valuable data. > > securityToken.getDomain() can be authenticated. > > On Mon, Dec 15, 2008 at 11:41 AM, Jamey Wood <[email protected]> wrote: > > Is there some relationship between the "container" param when a gadget is > > rendered (e.g. "ifr?container=shindig") and the associated > SecurityToken's > > domain value (e.g. "SecurityToken.getDomain())? At first glance, both > seem > > like ways to allow the Shindig server to customize its behavior for the > > consumer in some way (such as assuming there are entirely different > social > > graphs for "container1" and "container2"). > > > > Thanks, > > Jamey > > >
