Great! But then I'm a little confused about shindig's config file: "container.js". Is shindig the "container", or is it a "gadget server" for multiple containers.
In container.js, there is one setting for "parentRelayUrl". Couldn't that setting be different for each container? Maybe the containers could pass that setting in as a param? Similarly, the containers need to know where the gadget server's relay URL is. It seems "parentRelayUrl" is actually (or also) "gadgetRelayUrl", so is there a discovery mechanism for containers to fetch this (and possibly other) settings from shindig? Thanks, -Randy From: Chris Chabot <[email protected]> To: [email protected] Date: 10/02/2009 07:48 AM Subject: Re: Can multiple social sites share a single deployment of shindig? Hey Randy, Absolutely, in fact many deployments do actually use that already (Google being one example). The trick is to use the container param (which is part of the security token) and / or domain to know which data source the requests should be routed too. On Wed, Sep 30, 2009 at 5:07 PM, Randy Hudson <[email protected]> wrote: > I'm wondering about the intended/supported deployment topologies for > shindig. Is it possible to have multiple sites (i.e. the > top-level/container page) hosted on multiple servers but sharing a common > deployment of shindig for serving the rendered gadgets? Or is the > intended use that shindig is deployed along with each "social site" > requiring shindig's services. > > One reason I ask is that I see some config settings in shindig that refer > to properties of the consuming site. > > Thanks, > Randy Hudson
