We use option 1 via urlrewriteproxy. Works fine.
On 6/2/11 10:54 AM, "Li Xu" <[email protected]> wrote: > Stanton and Henry, thanks so much for all the suggestions! > > I listed all the 4 possible options below. We currently favor option1, the > most reliable one... Please suggest what do you think. > 1. Shindig consumer need to install a proxy component... > Shindig would require a patch to enable the usage of proxy ur if it's cross > domain xhr. > this seems to be the most reliable approach > 2. Enable Shindig RPC servlet to support CORS(CROSS Origin Resource Sharing) > Good potential, but has browser limitation...eg. pre IE8 browsers don't > support that > 3. JSONP... good alternative to CORS > some reading indicates there're security issues > 4. Use a hidden child iframe to point to the server which is at the different > domain and pass content back into parent frame > > thanks! > li >
