Comments on: Cross-site Ajax in Firefox 3

By: Chief Odie

Chief Odie — Wed, 18 Mar 2009 16:24:06 +0000

I don’t see any advantage to this other than simplicity.

To add to what Dan said, it’s also a case of security… You may be consuming a service that requires your clients to log-in individually. This allows the service to manage it’s own security without your site being the “Man in the middle”

Enjoy
Chief

By: anonymous

anonymous — Tue, 20 May 2008 10:41:30 +0000

Cross-site XmlHttpRequest feature is not supported anymore. Firefox 3 build 5 doesn’t support it!

By: dnix

dnix — Wed, 30 Apr 2008 16:05:56 +0000

Some of you guys are being fanboyish…IE has a rich administrative feature set that allows the cross domain issue to be managed atomically. FireFox got this wrong the first time around and enough folks with real jobs have complained about it all over the web to make it an issue.

By: nathj07

nathj07 — Mon, 21 Jan 2008 08:55:23 +0000

Desktop software has been able to do this sort of thing for while now. I think that is really a great step forwards. As a developer of many sites that often share information it would no doubt make my life easier. An obvious implementation is to have a page that returns XML with the standard data in it. The receiving page would then read this and format it using it’s own CSS.

By: Dan

Dan — Sun, 20 Jan 2008 03:13:52 +0000

@Dan Grossman – Great point on the bandwidth issue. However I don’t see the latter point as being all that strong. Just because.. and correct me if I’m wrong.. but it seems to me if you were utilizing a third party site / service it would most likely be open and/or you’d have permission to use it. Still a relevant point though.

If you delve in to the linked article it looks like they are working on implementing some simple access control for xml files, so that you can either allow anyone or only specific domains. pretty cool.. I haven’t seen that before.

By: Dan Grossman

Dan Grossman — Sat, 19 Jan 2008 20:50:19 +0000

But doing that in PHP means *you* use, and pay for, double the bandwidth of each request (download it from the remote server then serve it to your user). If you could do it with JS alone, the client takes the burden of the bandwidth bill. And it also prevents the 3rd party site from shutting all your users out by banning your IP — each request is coming from the individual browser.

By: Dan

Dan — Fri, 18 Jan 2008 19:44:53 +0000

I’d have to agree with php_penguin.. I don’t see any advantage to this other than simplicity. (Not that the alternative is really that hard…) By the way there is a great PHP class called snoopy, (source forge) that ties
in nicely with what we’re talking about…

By: Thierry

Thierry — Thu, 17 Jan 2008 10:35:32 +0000

Check my blog posts on the topic:

http://www.mellowmorning.com/2007/10/25/introducing-a-cross-site-ajax-plugin-for-prototype/

and

http://www.mellowmorning.com/2007/11/07/updated-cross-site-ajax-plugin-for-prototype/

By: XraySierra

XraySierra — Tue, 15 Jan 2008 15:55:30 +0000

I have to agree with Ruben. If this is not yet supported across most browsers (not even FireFox 2) then it is years off from practical use, am I wrong?

By: php_penguin

php_penguin — Tue, 15 Jan 2008 12:02:27 +0000

So why dont you just use PHP (or other SS language) as a proxy so it works with everything?