Hmmm... I guess I was unclear. So I want a page on my localhost to have a gadget embedded in it in an iframe. That page is essentially the commoncontainer index.html page which allows me to type in the url of any gadget and add it to the page. So I took the commoncontainer (just the javascript and html) and included it in my brand new webapp.
Then I changed the references in that to retrieve everything from my shindig server on another host, instead of locally (local worked). That's when I run into the problem of it making the rpc call to localhost instead of my other host hosting shindig. It sounds like from the previous thread I referred to that the google commoncontainer doesn't support this. I was thinking from the earlier conversation about security that you really wanted the webapp that will contain the gadget iframes to be separate from the shindig server. But maybe I'm totally misunderstanding. Thanks, doug On 3/28/11 5:20 PM, "Kris Vishwanathan" <[email protected]> wrote: > Interesting. I am not aware if anyone separating the common container from > Shindig. Usual practice is that applications in general are gadgets and you > will deploy Shindig and Gadgets in separate servers. Shindig server could > host entry point with bootstrap of common container, and gadgets coming > from various servers. Your app on the client side will be isolated into an > iframe. > > From your note its not clear what kind of an app you are referring. > >
