[webkit-dev] Out-of-process networking and potential for sharing memory cache (was Re: Feature Announcement: Moving HTML Parser off the Main Thread)

Maciej Stachowiak mjs at apple.com
Tue Jan 22 00:52:58 PST 2013

On Jan 22, 2013, at 12:17 AM, Sergio Villar Senin <svillar at igalia.com> wrote:

> En 21/01/13 23:07, Maciej Stachowiak escribiu:
>> On Jan 21, 2013, at 11:23 AM, Adam Barth <abarth at webkit.org> wrote:
>> Thanks, Adam. It's fine to pick up the conversation later, and we're certainly open to iterating beyond what we do first.
>> We're also happy to meet with anyone interested in this topic to discuss in person, or to document more of our design decisions in writing if the community would find that helpful. 
> That'd be awesome, at least an overview document that could help people
> to understand the whole picture and the main advantages/drawbacks of the
> selected design.

What topics are you interested in? I could probably write decent explanations of:

- NetworkProcess: tradeoffs for making it a process vs a thread in the UI process
- Load interception for proxying - ResourceHandle vs. ResourceLoader layer, pros and cons for each
- What code runs inside the network process, exactly?

Any other topics folks would be interested in?


More information about the webkit-dev mailing list