Using both Socket and RPC from 1 doc?

[emirotin]

I have the following architecture:

parent page (3rd party domain) http://brand.com/page.html
    -> js file (my domain) http://me.info/script.js
        -> it loads an iframe (my domain) using the Socket http://me.info/iframe.html

The script and the iframe have to communicate for several reasons (resizing, doing some actions on the parent page based on the clicks inside of the iframe, etc) At the same time, the iframe needs to use (and was using) the Rpc for the API server communication (our service as well, but on a different domain http://me.apis.org/, having the cors/ineex.html and all that stuff)

The 2nd part Rpc is already tested and worked just fine (get, post, put) - everything was OK. But that time I was loading an iframe y manually adding it to the container

No, after the iframe was loaded using the Socket call the Rpc messages are not going to the server - instead they go to the parent page.

[michikono]

+1

[prostoandrei]

+1