Re: Multiple sockets and noConflict

[Jonas.Hartwig]

I continued investigating the issue:
 1. LinkedId uses noConflict too.
 2. LinkedIn uses RPC instead for sockets.
 3. if i open the embedded iframe created by easyXDM in a separate browser window the LinkedIn buton starts working if I remove all easyXDM related query parameters and reload the page.

Don't know if that is useful. I will continue to investigate.

Still hoping for some tips though :)

regards

On Friday, 28 September 2012 16:12:30 UTC+2, Jonas.Hartwig wrote:

Hi all.

I tried to figure out on how to make the following working:

I have a website (parent) which creates a socket to an iframe via easyXDM. Both ends (the iframe and the parent side) communicate without any problems or difficulties.  Inside the iframe is a LinkedIn share button. LinkedIn uses easyXDM as well to transfer a json object. This json object for some reason ends up on my web site (parent) which makes the linked in button unusable and results in a wrong target location. Here is the example page: http://www.cision.com/uk/news-room/#!/pressroom feel free to try it urself.

code on the parent which creates the socket:
            if (window.easyXDM)
                window.lib = { easyXDM: easyXDM.noConflict("cwsync") };
            window.lib.socket = new window.lib.easyXDM.Socket({
                remote: url,
                props: { style: { width: "100%", padding: "0px 0px 10px 0px" }, id: "CisionRemoteContent", scrolling: "no" },
                container: container,
                onMessage: function (message, origin) {
                    //here arrives twitters json
                },
                onReady: function () {
                    //...
                }
            });

script on the iframe (the other side of the socket):
            if(window.easyXDM)
                window.lib = { easyXDM: easyXDM.noConflict("cwsync") };
            window.lib.socket = new window.lib.easyXDM.Socket({
                onReady: function () {
                    //...
                },
                onMessage: function (message, origin) {
                    //...
                }
            });


regards
  Jonas

[Jonas.Hartwig]

I did not find any solution ...

[Øyvind Sean Kinsey]

This is due to the instance of easyXDM in the intermediary page acting as a provider instead of a consumer (easyXDM automatically picks up the arguments passed in the url).

I'll forward this to my contact at IN - a flag can probably be set to avoid easyXDM acting as a provider.

Øyvind Sean Kinsey
San Francisco, CA

[Jonas.Hartwig]

Thanks, may you please inform me about any news?!

[Jim Spath]

I am also experiencing issues using LinkedIn within an already established easyXDM iframe.

Was there any resolution to this issue?

[Jim Spath]

I was able to edit the easyXDM source and add support for overriding the normal 'xdm' parameter prefix.  When I did this, I was able to get the LinkedIn follow button to show up in my easyXDM created iframe.

This seems like something people might be interested in ... should I fork easXDM on github and add this?

[Jim Spath]

I've made a pull request that adds the necessary prefixing support to easyXDM

https://github.com/oyvindkinsey/easyXDM/pull/228

All the tests seem to work, and LinkedIn is now working properly in my easyXDM Iframe.

[Jonas.Hartwig]

nice work. i will look into it asap :)

[Øyvind Sean Kinsey]

I just replied on https://github.com/oyvindkinsey/easyXDM/pull/228 with some comments :)

Øyvind Sean Kinsey
San Francisco, CA

--
You received this message because you are subscribed to the Google Groups "easyxdm" group.
To unsubscribe from this group and stop receiving emails from it, send an email to easyxdm+u...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.