easyXDM

v2.3.1 – bugfix

v2.3.1 contains a fix for a bug in the new NixTransport. This bug would cause the ‘onReady’ function to be called prior to the constructor returning – meaning that the reference to the transport/rpc would still be undefined.

v2.3.0 is out

As announced earlier, work has been done to a new transport that targets IE6 and IE7 specifically. This transport has now been improved and RPC-calls made are now actually using as little as  ’0′ milliseconds (very little that is) back and forth – that is actually faster than postMessage in Chrome! The effect of this new transport is that if you are targeting IE6+, Opera 9+ Firefox...

new transport for IE6/7, as fast as postMessage, and with NO dependencies!

Until now, if you wanted hi-speed communication in IE6/IE7 you would have to resort to the NameTransport, but this has its drawbacks It makes a ‘rattling’ sound when it navigates the documents It requires a html-file, name.html, present on both of the servers. Especially the last issue is a tough one, as many aren’t necessarily able to upload any files to the servers. (more…)

v2.2.0 is out

Recently I have dived back in to the RPC feature and I have managed to improve this quite a lot. No more isVoid/isAsync These are no longer needed as all of this is automatically handled by the RpcBehavior. Optional callbacks when calling methods, success, success+error, or none if the remote method does not return data or you just don’t care about it A shorthand notation for defining local...

easyXDM and prototype.js, how to make it work

This is no longer needed from v2.1.0 as easyXDM now feature tests for a valid JSON implementation. Cross-domain RPC was made easy by the introduction of easyXDM, but there are still obstacles to be found, especially when using libraries like PrototypeJs due to it extending the browser in unsound ways. Specifically, when it comes to PrototypeJs,  it augments the Array objects prototype with an .toJSON...

easyXDM 2.0, now even with a new website!

Finally, the new easyXDM v2.0 is here! This is really not just an incremental update, but instead, it builds on the internal changes made > 1.7.0 and exposes this using a new, simpler, but still familiar API. This also means that you cannot just drop the new version in and expect it to work, you need to realign you code with the samples (which there are many of on these pages), but this shouldn’t...