This is how we are designing the Pepper API [1] by the way. It is designed
to be layered in order to support an optional, out-of-process
implementation.
I've always been interested in a similar model for WebKit.
-Darin
[1] https://wiki.mozilla.org/Plugins:PlatformIndependentNPAPI
On Fri, Apr
On 4/9/2010 9:06 AM, Darin Adler wrote:
The prototype works with both a threaded model and a multiple process model,
chosen at runtime.
That's good to hear, because also there are some platforms where
creating multiple user processes is not allowed.
-Benbuck
The prototype works with both a threaded model and a multiple process model,
chosen at runtime. It seems worthwhile to keep this feature.
Anders told me he often turns on the threaded model to debug since the
development tools we have work better with a single process and multiple
threads than
The OpenGL approach to this problem is to have two layers with the
same API. (Sorry my diagrams aren't as awesome as Maciej's.)
Application
--- WebKit2 API ---
Multiproc client implementation
=== Process Boundary ===
Multiproc server implementation
--- WebKit2 API ---
Singleproc implementation
We
4 matches
Mail list logo
