Peer to Peer Render Process communication

[nvine]

Hello,
I have a scenario in which there is an application with multiple Cef3 browser instances. These browser instances need to communicate with each other, like ex: access some css properties in each other's DOM etc.,
Does Cef3 provide Peer to Peer Render Process communication which correspond to different browsers? From what I have studied, I haven't found any APIs for this. So the method I am planning to employ is,
1. Each renderer process also has a TCP server running in separate thread which receives JSON data, and evaluates the result and returns the JSON.
2. The browser process indicates each render process the port that can be used for communication via CefBrowser::SendProcessMessage
3. The JS in render processes now start communicating via native callbacks which use the socket or pipe to communication with process as described in 1.
Will this approach work or are there any considerations I am missing above?

Also what would be the effort to bring in chrome extension sort of mechanism in CEF3, just curious, since what I am trying to achieve is similar to an extension.

Best Regards,

[magreenblatt]

Your proposed approach will break once CEF3 supports sandboxing. Instead, you should use IPC via SendProcessMessage and have the browser process route the messages between renderers.

Chrome extensions require a lot of code that doesn't exist and can't easily be ported to CEF3. If you need an extension concept you'll need to implement it in your application.