There is a client executable and the libcef dynamic library. The secondary processes can be launched using the same client executable or a separate executable (see the CefExecuteProcess function). There will likely be some limitations on this if you want the renderer process to be sandboxed.

fddima wrote:UPD: It can be shared across many client executables? I.e. perform separate 'install'.

There is a client executable and the libcef dynamic library. The secondary processes can be launched using the same client executable or a separate executable (see the CefExecuteProcess function). There will likely be some limitations on this if you want the renderer process to be sandboxed.

Flexible enought. It is cool. Personally i'm think that sandboxing it is optionally thing. For example, for me, i'm run only own pages without any chance to get executed 3rd-party untrusted code and pages. I think it is true for many CEF users. Also, at last holidays i got my wife's sister notebook with many soft installed, and google chrome doesn't show any pages without --no-sandbox switch -- i mean that sandboxing it is cool feature, but really not so good, as it advertised.

fddima wrote:UPD: It can be shared across many client executables? I.e. perform separate 'install'.

Installation is the same as with CEF1.

I mean, that will be cool in addition to current deployment strategy, allow second - share official cef releases per machine. It is not so complex for windows, and much more natural for linux-way, as i think.Mainly it is affect only to "path problems" in cef (may be already fixed in cef1) and may be require some "running" stub what needed to included per application (which know how resolve location of installed 'runtime').

Once CEF3 has feature parity with CEF1, is the plan to stop adding new features to CEF1 (essentially switching it to more of a "maintenance mode")? Do you have a vague ETA for when you would expect CEF3 to be feature complete?

emerick wrote:Once CEF3 has feature parity with CEF1, is the plan to stop adding new features to CEF1 (essentially switching it to more of a "maintenance mode")?

My hope is that everyone will eventually be able to move from CEF1 to CEF3. No feature freeze is currently planned for CEF1 and any future decision along those lines will be largely based on community feedback.

emerick wrote:Do you have a vague ETA for when you would expect CEF3 to be feature complete?

The first binary release of CEF3 will probably be within the next few months. Feature completeness with CEF1 will likely be a moving target for a while. I'll provide more information about my personal priorities for that initial release in the near future. Others are welcome to indicate their personal priorities by starring the associated issues in the CEF issue tracker .