Comments on: easyXDM – extremely easy cross-domain scripting

By: Kieth Raggio

Kieth Raggio — Sun, 05 Sep 2010 12:40:36 +0000

What a blog post!! Very informative also easy to understand. Looking for more such blogposts!! Do you have a twitter or a facebook?
I recommended it on digg. The only thing that it’s missing is a bit of color. However thank you for this blog.

By: Nathaniel Benedict

Nathaniel Benedict — Sun, 05 Sep 2010 01:05:11 +0000

What a comment!! Very informative and easy to understand. Looking for more such blog posts!! Do you have a twitter or a facebook?
I recommended it on stumbleupon. The only thing that it’s missing is a bit of new design. However thank you for this information.

By: Hilary

Hilary — Fri, 12 Mar 2010 01:53:27 +0000

I'm also having the same issues in IE7 / XP and IE6 / XP.

Thanks.

By: Widget support added to easyXDM! | Rantings in the dark

Widget support added to easyXDM! | Rantings in the dark — Mon, 08 Feb 2010 23:21:24 +0000

[...] These make it extremely easy to make mashups based on the subscribe/publish architecture. To read more about easyXDM check out this blog post. [...]

By: Øyvind Sean Kinsey

Øyvind Sean Kinsey — Wed, 03 Feb 2010 10:15:46 +0000

For those concerned about the size limit in IE6 and 7 due to the use of HashTransport – there is now a new fallback transport available, the NameTransport (http://easyxdm.net/docs/?class=easyXDM.transport….
As far as I have seen, this can handle >150k messages
Note that you need to supply a new parameter, remoteHelper for this to kick in!

By: oyvind.kinsey

oyvind.kinsey — Sat, 02 Jan 2010 20:09:06 +0000

And its out! See http://kinsey.no/blog/index.php/2010/01/02/easyxdm-just-became-even-easier-to-use/ for more.

By: oyvind.kinsey

oyvind.kinsey — Sat, 02 Jan 2010 16:14:28 +0000

Just consider the consequences of how the jQuery plugin falls back to modifying the hash of the parent frame, and how it needs the exact url of the page.
One of the important goals of easyXDM is to be nonobtrusive, that is, not modifying any of the behavior on the primary page, and modifying the url of the main page, and also jQuery as a dependency, is what I consider obtrusive.
I’ll release a version that will be able to utilize any file located on the main domain, like robots.txt or favicon.ico later tonight – I’ll give you a heads up.

By: meinhard

meinhard — Sat, 02 Jan 2010 15:29:13 +0000

Thanks for considering. Unfortunately the market share of StupidBrowsers (TM) is still quite high. I went for the jQuery postMessage plugin for now, which uses location hash modification as fall-back. I will keep an eye on easyXDM.

By: oyvind.kinsey

oyvind.kinsey — Sat, 02 Jan 2010 11:20:24 +0000

Hash.html is only used to support older browsers that does not support the postMessage interface, so if you can live without this, it will still work.
I’m going to see if I can get something to work that doesn’t rely on the user having to upload files – maybe by using the robots.txt file or something, but this will not be as efficient.

By: meinhard

meinhard — Sat, 02 Jan 2010 01:38:15 +0000

The users of our planned API sometimes do not have the possibility to upload HTML files. So the current hash.html solution would be a showstopper for us.