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

Jochen Eisinger jochen at chromium.org
Mon Oct 8 10:52:45 PDT 2012


can you share your plan how to prioritize network requests in the network

It's a long standing issue of the chromium port (and I believe the
blackberry port is affected as well) that a ResourceRequest doesn't know
whether it was created for e.g. an XHR or a main document load, which makes
it difficult to prioritize the requests.

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.


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/32766506/attachment.html>

More information about the webkit-dev mailing list