[webkit-dev] WebKit2 SharedSecondaryProcess model
kb at inf.u-szeged.hu
Wed Sep 1 04:09:48 PDT 2010
(Sorry for flooding the list but I need to repeat my reply to put it in
the right thread.)
Seems like I misunderstood the concept. I assumed that the shared
process model means that there could be multiply UI process instances
that uses the same web process, virtually when the second MiniBrowser is
launched it connects to the existing web process. By taking a deeper
look into the WebContext and WebProcessProxy classes, I have realized
that the shared process model is about using one web process for
multiply views (what is cool) and not for multiply processes (what would
be more cool from my point of view :) ).
What do you think about my idea? Primarily on embedded devices it
would be great to use the web engine as a server process because it
could save a lot of memory. I think the current design is not too far
for supporting that. Mainly we should find a correct way of connecting
the new UI process to the existing web process, and the Connection
should be per page instead of per process (or we should rework the
WebProcess to not be a singleton?).
Please provide some feedback on this because it is important for our
project to know which way should we go on with WebKit2. Thank you!
On 08/30/2010 08:22 PM, Sam Weinig wrote:
> Hi Balazs,
> Does it not work currently? If not, can you please file bugs on what
> is not working. We plan on making the shared process model the default
> model for the API, but it will probably have the caveat that it will
> not support InjectedBundles.
> On Mon, Aug 30, 2010 at 6:08 AM, Balazs Kelemen <kb at inf.u-szeged.hu
> <mailto:kb at inf.u-szeged.hu>> wrote:
> Hi all!
> I am wondering about do you plan for the mac and win to support the
> shared web process model?
> Actually, I have played around with that for Qt. I have a working,
> of concept implementation. The visited links and the back-forward list
> features are broken, but apart from that the browsers are working with
> the shared web process. I had to rework common parts of the code for
> achieving that, and I would like to contribute it in small parts. I
> think if we want to support that model in the future than we should
> start to implement it as soon as possible to assure that our
> design fits
> the needs of that.
> Balazs Kelemen
> webkit-dev mailing list
> webkit-dev at lists.webkit.org <mailto:webkit-dev at lists.webkit.org>
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the webkit-dev