One of the bigger advantages is to avoid duplication of your pages in search engine results, as this will actually bring your overall page weightings down.

Tanny O'Haley said on December 06, 2006

It's not only sub-domains, but directory paths too. www.example.com/web/util and www.example.com/app are considered different domains. I had to use document.domain = "example.com"; on all pages so that the directories could talk to each other's pages.

t3knomanser said on July 06, 2007

Holy crap, the cross-domain JSON scares me. That's amazingly dangerous! Really simple, sure- but wow, that's a lot of trust on the provider of the data.

Motin said on August 17, 2007

One implementation of the first method is AJAX Extended that sould be found on ajaxextended.com but that domain, the author and his company seems all to have vanished totally!

I found the client part of AJAX Extended here: http://www.ajaxlessons.com/?attachment_id=19

Anyone know where I can get a hold of the AJAX Extended PHP API source code which is needed as well...?

Motin said on August 17, 2007

Found a mirror finally - Google Code: http://google.com/codesearch?hl=en&q=show:M8cy5FPc_s0:A16F7hY_YnM&sa=N&ct=rdp&cs_p=http://svn.serebryakov.ru/ajaxextended/trunk

Girish said on November 16, 2007

Another interesting approach to the same cross domain problem with a proxy. This time with an added functionality to handle the cookies returned by the requested page.


http://icodeleague.110mb.com/cmsimple/index.php?Website_Development:Cross_Domain_AJAX

Henrik said on November 21, 2007

Yet another solution for PHP developers:

http://redotheweb.com/?p=4

Jason Miller said on September 13, 2008

You can actually make a "real" Cross Domain Request using iframes (yes, the devil) - though you have to be able to stomach their use. I created a JavaScript library to bring a little more ease to the process here: http://developit.ca/XDR-JavaScript-Cross-Domain-Request/.

Kyle Simpson said on January 30, 2009

I've got a project called 'flXHR' http://flxhr.flensed.com/ which is a flash+javascript direct re-implementation of the native XHR api, but using an invisible flash object to allow cross-domain requests. Since it's API is identical, it's an easy drop-in replacement for native XHR, and can thus be used very easily with any existing code or JS frameworks (like jQuery, Dojo, etc).

Since it uses flash (specificaly 9.0.124+), it utilizes the newest, strongest implementation of Adobe's cross domain server opt-in policy to authorize such communication, which makes the communication using flXHR inherently more secure, more efficient, and less hacky than many of the other common cross-domain workarounds available right now.

In addition, by centering on the native XHR API, flXHR becomes an effective "future-proof" drop-in solution until such time as browsers extend those API's to allow for native cross-domain-safe communication.

Stefano Crosta said on February 24, 2009

Nice summary Jonathan!

At dev.mixendo.com we are working to facilitate bulding mash-up applications, and the same-origin policy is the first lock to break.

We implemented an improved version of the "cross-domain proxy" solution described here, the only one that does not require any access to the servers you want to connect to. Improved, because we also manage cookies for persistent sessions, and have an improved security model limiting cross-domain to a self-declared list of hosts that the user will be able to validate.

Usage of our service is extremely simple, you integrate our javascript and keep using the XMLHttpRequest as before... except now it's cross-domain enabled!

Stefano Crosta said on February 24, 2009

Nice summary Jonathan!

At dev.mixendo.com we are working to facilitate bulding mash-up applications, and the same-origin policy is the first lock to break.

We implemented an improved version of the "cross-domain proxy" solution described here, the only one that does not require any access to the servers you want to connect to. Improved, because we also manage cookies for persistent sessions, and have an improved security model limiting cross-domain to a self-declared list of hosts that the user will be able to validate.

Usage of our service is extremely simple, you integrate our javascript and keep using the XMLHttpRequest as before... except now it's cross-domain enabled!

Sorry, comments are closed for this post. If you have any further questions or comments, feel free to send them to me directly.
久久中文字幕免费高清,三级在线看中文字幕完整版,中文字幕偷乱视频在线