[webkit-dev] Discussing bug 98539 - Refactor resource loading to allow for out-of-process loading and memory caching

Brady Eidson beidson at apple.com
Mon Oct 8 11:23:42 PDT 2012


On Oct 8, 2012, at 10:52 AM, Jochen Eisinger <jochen at chromium.org> wrote:

> Hey,
> 
> can you share your plan how to prioritize network requests in the network process?
>> We currently work around that issue by adding a TargetType to ResourceRequest which is however a layering violation which I'd like to get rid of.

Since the NetworkProcess management will be contained in WebKit 2 it won't be an equivalent layering violation for that port.

If that explanation doesn't make sense then I might have misinterpreted your concern.

On a slightly different note it seems reasonable to me that a WebCore ResourceRequest have target-type/priority-type information attached to it.

I don't know if doing that has come up in the past and different conclusions we reached.  I haven't placed a lot of thought into that since it doesn't seem directly necessary for this effort.

~Brady

> 
> best
> -jochen
> 
> On Mon, Oct 8, 2012 at 7:39 PM, Brady Eidson <beidson at apple.com> wrote:
> A bit of background:
> 
> A few of us have been working on enhancing WebKit2's support for multiple WebProcesses.  As part of this effort I'm working on https://bugs.webkit.org/show_bug.cgi?id=98537 - "Add a NetworkProcess to WebKit2"
> 
> One benefit of the NetworkProcess will be to have a single shared process doing network i/o on behalf of all attached WebProcesses.
> 
> Another benefit we've identified is the ability to have that process also act as custodian for a shared memory cache amongst the attached WebProcesses.
> 
> While this effort is primarily about WebKit 2, making it possible will obviously involve some changes to the WebCore memory cache and resource loading.
> 
> I don't plan to shoehorn in changes, but rather to make sensical refactoring that cleans up the code for all ports.  Anyone familiar with the CachedResource and ResourceLoader mechanisms probably know they're not really up to the clarity and quality standards we strive for, and I'm excited about being able to focus on them for awhile and make them better for everyone.
> 
> I have a few patches lined up locally to do this and have attached the first of these to https://bugs.webkit.org/show_bug.cgi?id=98539
> 
> Feel free to share concerns here or in the collection of bugzillas that will slowly be growing as I make progress.
> 
> ~Brady
> _______________________________________________
> webkit-dev mailing list
> webkit-dev at lists.webkit.org
> http://lists.webkit.org/mailman/listinfo/webkit-dev
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-dev/attachments/20121008/fc97cc1a/attachment.html>


More information about the webkit-dev mailing list