Can you expound on that? What do you mean you made the metadata call server side? What did you modify to do this? Won't I still have issues making other calls. Won't the web app on my localhost still use the relative path to make gadget API calls? I'm not sure I understand how the %host% substitution happens for the entries in container.js.
Sent from my iPad On Mar 30, 2011, at 4:34 AM, "Christiaan Hees" <[email protected]> wrote: > I ended up doing the metadata call on the server side instead of the > client to avoid this issue and it works. But this is still using the > old container code, so I'm not sure if it's the best solution for you. > > On Wed, Mar 30, 2011 at 3:50 AM, Davies,Douglas <[email protected]> wrote: >> I'm pretty sure it's just using one of the relative urls from container.js, >> because I know that if I modified all the urls on the server side I then saw >> it making the request to the shindig server correctly. However that request >> fails because there is no post data in the request for gadget metadata. Not >> sure if that is a cross domain issue or something else. Hopefully someone >> will have an idea. Thanks. >> >> Doug >> >> Sent from my iPhone >> >> On Mar 29, 2011, at 9:18 PM, "Ryan J Baxter" <[email protected]> wrote: >> >>> Hi Doug, I think you are right you should be striving for situation 3, at >>> least that is my understanding. We have not yet tried to separate Shindig >>> and the web app so they are running on two different domains. The only >>> thing I can suggest is just diving into the common container code and >>> figure out how it is figuring out the domain to use. Off the top of my >>> head I cannot recall how the common container is doing this. Mike >>> Hermanto may know more.... >>> >>> -Ryan >>> >>> Email: [email protected] >>> Phone: 978-899-3041 >>> developerWorks Profile >>> >>> >>> >>> From: "Davies,Douglas" <[email protected]> >>> To: Kris Vishwanathan/Fairfax/IBM@IBMUS, <[email protected]>, >>> Date: 03/29/2011 04:35 PM >>> Subject: RE: Shindig and webapp on same host/domain or not? >>> >>> >>> >>> Hmmm... Now I am seriously confused. I'm not sure we are both using the >>> same terminology here. >>> >>> I want this >>> >>> Server 1 (domain x) >>> ------------------ >>> Shindig Server >>> >>> Server 2 (domain y) >>> ------------------ >>> A webapp that uses javascript gadget api to communicate with shindig >>> server and render gadgets into iframes >>> >>> The problem is that server 2 is trying to call itself for the gadget api >>> calls, since the container javascript is using relative paths. >>> >>> As Isaiah then mentions, he is trying to do a rewrite rule on server 2 >>> to redirect the requests to the shindig server, however I suspect he'll >>> run into cross-domain issues here (as suggested by the common container >>> issue thread I referred to earlier). >>> >>> I'm sure there is just some configuration or concept I am missing here. >>> >>> doug >>> >>> -----Original Message----- >>> From: Kris Vishwanathan [mailto:[email protected]] >>> Sent: Tuesday, March 29, 2011 3:27 PM >>> To: [email protected] >>> Cc: Davies,Douglas; [email protected] >>> Subject: Re: Shindig and webapp on same host/domain or not? >>> >>> Scenario three is a reasonable approach and that's how most of the >>> Social >>> networking sites run. >>> >>> Your deployment can look as below: >>> >>> Server1 (Domain X) >>> ------------ >>> >>> Shindig Server >>> Common Container >>> index.html or your webpage that bootstraps container and your page etc.. >>> >>> >>> Server 2 (Domain Y) >>> ------------- >>> Your custom webapp >>> Other gadget apps >>> >>> >>> Hope it helps. >>> >>> Thanks and regards >>> >>> Kris Vishwanathan >>> >>> >>> >>> >>> >>> >> >> >
