Thanks a lot, Doug. UrlRewriteFilter works! ----- Forwarded by Li Xu/Raleigh/IBM on 06/10/2011 03:09 PM -----
From: daviesd <[email protected]> To: Li Xu/Raleigh/IBM@IBMUS Date: 06/09/2011 10:49 AM Subject: Re: problem resolving "%host%" in jsonrpctransport.js when separating server and web page container See http://shindig-dev.markmail.org/search/?q=davies#query:davies%20order%3Adate-backward+page:2+mid:nicfkr4etzo2oa2k+state:results Let me know if you have any other questions. doug On 6/9/11 10:37 AM, "Li Xu" <[email protected]> wrote: Great to hear. Just curious, would you please share more details ? I have to modify the shindig client side js to rewrite the url to go thru proxy... thanks, li daviesd ---06/02/2011 01:22:46 PM---We use option 1 via urlrewriteproxy. Works fine. On 6/2/11 10:54 AM, "Li Xu" <[email protected]> wrot From: daviesd <[email protected]> To: <[email protected]> Date: 06/02/2011 01:22 PM Subject: Re: problem resolving "%host%" in jsonrpctransport.js when separating server and web page container 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 >
