Comments on: v2.4.4 – New feature and bug-fix release https://easyxdm.net/wp/2010/08/02/v2-4-4-new-feature-and-bug-fix-release/ Cross-Domain Messaging made easy Thu, 20 Apr 2017 18:47:42 +0000 hourly 1 https://wordpress.org/?v=4.9.34 By: Øyvind Sean Kinsey https://easyxdm.net/wp/2010/08/02/v2-4-4-new-feature-and-bug-fix-release/comment-page-1/#comment-531 Wed, 06 Apr 2011 09:02:00 +0000 http://easyxdm.net/wp/?p=335#comment-531 Well, I’d say it’s better.
They both do roughly the same, and provide the same mechanisms for transport (easyXDM does not provide flash, but thats only because there has been no need), but easyXDM is as you say standalone, and does more of the legwork for you while at the same time being quite configurable.

Personally I also feel that the overall code quality is better – it uses feature detection where goog uses user agent sniffing, and its structure is easier to follow.

Also, does a lot to ease RPC, as you can see by the examples.
But don’t take my word for it – ask twitter, disqus, linkedin or many of the others why they opted for it 🙂

]]> By: Jh https://easyxdm.net/wp/2010/08/02/v2-4-4-new-feature-and-bug-fix-release/comment-page-1/#comment-528 Tue, 05 Apr 2011 22:31:00 +0000 http://easyxdm.net/wp/?p=335#comment-528 How does this compare to goog.net.xpc.CrossPageChannel of Closure Library?
Are there any specific things that this implements over Closure’s implementation?
Other than of course that this library is standalone and not structured to be specifically used with Closure.

]]>