>From what I understand rpc_relay setup is only needed if you are using the ifpc transport for rpc. You can force this by setting useLegacyProtocol in your container config but why you would want to do that I do not know. With modern browsers (html5) Shindig makes use of window.postMessage (wpm) to do rpc and you don't have to worry about the relay setup. In general the fallback for non-html 5 browsers is using a flash technique if possible. If you're interested in the way the rpc transport is chosen, you can check out rpc.js#getTransport() for more info.
-Stanton From: "Davies,Douglas" <davi...@oclc.org> To: <dev@shindig.apache.org>, Date: 03/21/2012 20:28 Subject: Re: Shindig running on different domain than container REVISITED Thanks Stanton. So no rpc_relay setup etc.? Seems last time I did this I ran into that. Doug Sent from my iPhone On Mar 21, 2012, at 3:43 PM, "Stanton Sievers" <ssiev...@us.ibm.com> wrote: > Hi Doug, > > Yes, things work just fine running the container page and shindig on > different domains. You can set the osapi.container.ServiceConfig.API_HOST > and osapi.container.ServiceConfig.API_PATH when creating your > osapi.container.Container object to get the right pointers in place. > > Best regards, > -Stanton > > > > From: daviesd <davi...@oclc.org> > To: shindig <dev@shindig.apache.org>, > Date: 03/21/2012 13:04 > Subject: Shindig running on different domain than container > REVISITED > > > > About a year ago there was a discussion about shindig running on a > different > domain than the container. > > http://permalink.gmane.org/gmane.comp.web.shindig.devel/6824 > > Up till this point we have been running our shindig servers and our > container webapps on the same domain. We¹d like to move away from this. > Is > this possible with shindig 2.5.0? Have there been changes since this > discussion? If so, is there documentation on what configuration needs to > happen to get this to work? > > Thanks, > Doug > >
