Assuming you have one host/server that you can fully configure I would just proxy the requests to the correct location. To make things easy I would group remote services under a common URL prefix, something like example.com/services/*, so you only need a single proxy rule.
We use this approach for serving static content directly from load balancers and all remote/service calls are proxied to different app servers. Works pretty well and it allows us to do other nice things that wouldn't be possible without such a proxy. -- J. -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/google-web-toolkit?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
