Comments on: Cross domain iframe communication without location polling

By: oyvindkinsey

oyvindkinsey — Tue, 25 Aug 2009 22:08:35 +0000

this just what easyXDM is, a library that uses the best metod, postMessage or hash/fragment to communicate.

By: soldair

soldair — Tue, 25 Aug 2009 09:31:32 +0000

A while back there was a post about how to use postMessage for x domain iframe communication. A solution like this should check for postMessage support and not bother creating proxy frames. perhaps it could even provide backwards support for the html5 post message api.
I have put an example of 2 way communication with HTML5 postMessage on http://ryanday.org i hope it helps someone =).

By: dawesi

dawesi — Tue, 25 Aug 2009 01:56:09 +0000

Never had problems with cross domain stuff using ExtJS… just use the inbuilt proxies…

By: oyvindkinsey

oyvindkinsey — Mon, 24 Aug 2009 20:50:55 +0000

Unfortunately this example seems not to work in IE6, an my own experiments with the resize event has also so far been unsuccessfull with IE6.
I have on the other hand had success using a #top fragment coupled with a onscroll event, working on integrating that into easyXDM (http://kinsey.no/blog/index.php/2009/08/20/easyxdm/) now.

By: eyelidlessness

eyelidlessness — Mon, 24 Aug 2009 19:16:31 +0000

“IFrames are expensive in terms of memory and time to create and destroy. Probably not an issue for a one-off message you want to throw over the wall, but throw-away iframes become an issue in a high volume long life reliable data channel between A and B.”

Nevermind leaks!

By: dannythorpe

dannythorpe — Mon, 24 Aug 2009 17:22:05 +0000

The cross-domain channel library developed for Windows Live’s contacts web control back in 2006/2007 used a permanent iframe endpoint. Here’s an article about it:
http://msdn.microsoft.com/en-us/library/bb735305.aspx Derivatives of this library are now being used by other Microsoft web applications (alongside HTML5 message passing and other techniques when available – the iframe technique is the absolute last resort, but it does work everywhere).

IFrames are expensive in terms of memory and time to create and destroy. Probably not an issue for a one-off message you want to throw over the wall, but throw-away iframes become an issue in a high volume long life reliable data channel between A and B.

-Danny

By: marlonbtx

marlonbtx — Mon, 24 Aug 2009 15:58:21 +0000

does anyone knows how to upload files using crossdomain ? and handling the readystate or onload event

By: oyvindkinsey

oyvindkinsey — Mon, 24 Aug 2009 14:34:47 +0000

I am actually working on using the resize technique in the easyXDM library, I had a working prototype of it earlier but it got lost.

Btw, any chance your gonna post about easyXDM anytime soon?

By: meandmycode

meandmycode — Mon, 24 Aug 2009 10:35:29 +0000

I’ve got to be honest, whilst polling for a change isn’t the proudest moment, it works fine.. a year from now we can probably expect most browsers to have native events anyway.

By: steida

steida — Mon, 24 Aug 2009 10:30:32 +0000

Such technique will never work in IE7. Some tomfool from MS IE team decided that changing location should make disturbing click sound. This repulsive behavior can’t be disabled, so for each message, a new iframe has to be created, which is the only way to suppress clicking sounds.