The way you would normally implement something like this is by using a reverse proxy in front of both of your back ends. Apache httpd, lighthttpd, and squid are all pretty good at this for most usage. There are more specialized projects as well.
squid will generally perform the best of these options, though httpd (with mod_proxy) is generally easiest to set up. On Fri, May 1, 2009 at 7:54 PM, jay patel <[email protected]> wrote: > Hi Shindig Team, > > I am trying to run gadgets and social projects on separate servers. As > javascripts for social feature is served by the "gadgets server" (and, not > by the "social server"), browser complains when javascript for social > feature tries to access rest/rpc services from "social server". Is there > any > solution implemented in current shindig (such as proxy/jsonp...etc) to > overcome this. > > I really do not want gadget and social projects on one server instance...I > want to keep "gadget server" and "social rest/rpc server" separate. > > My gadget server is running on localhost:8080 and social server on > localhost:8081..both servers are Jetty. I am using the latest code from the > trunk. > > Thanks for your time, > > Jay >
