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
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
On Thu, Apr 8, 2010 at 4:01 PM, Anders Carlsson wrote:
> WebKit2 is designed from the ground up to support a split process model,
> where the web content (JavaScript, HTML, layout, etc) lives in a separate
> process. This model is similar to what Google Chrome offers, with the major
> difference b
3 matches
Mail list logo
