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
