magreenblatt wrote:I originally considered this but decided that the performance would be sub-optimal in many cases due to data being passed between processes unnecessarily. Instead, the application uses CefProcessMessage for communicating between processes and JS bindings are in the renderer process only. This allows for application-level optimization of both communication and bindings (JS API). So, for example, you can pass all of an object's attributes as a single CefProcessMessage and create a binding that exposes them to JS as separate accessors without additional inter-process communication. Design your JS APIs to work asynchronously as described here: http://www.chromium.org/developers/desi ... design-doc
I'm absolutely agreed with idea to minimize inter-process interactions, but from api headers i'm still little misunderstood how it work, i'm doesn't see any usage of CefProcessMessage. As i understand, that it will be possible to send custom message from JS to UI process and handle them, even without 'classic' JS bindings?