[Webkit-unassigned] [Bug 25436] New: Refactor appCache for use in multi-process browsers

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=25436

           Summary: Refactor appCache for use in multi-process browsers
           Product: WebKit
           Version: 528+ (Nightly build)
          Platform: All
        OS/Version: Mac OS X 10.5
            Status: UNCONFIRMED
          Severity: Normal
          Priority: P2
         Component: WebCore Misc.
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: michaeln at google.com
                CC: andersca at apple.com, michaeln at google.com,
                    jorlow at google.com


This bug is to track the first step in getting appCache working in
Chromium.  The high level plan was discussed offline with Brady, Maciej,
Anders, and Sam.

The basic idea is to have a clear split between a "front end" and a "back end"
of the appCache. The two will call each other in such a way that a proxy layer
can be added in between.

This document provides an overview of this approach.
http://docs.google.com/Doc?id=dvvc3n9_0dkfddscs
The language in that doc (at this moment) is a little stale and doesn't reflect
our desire to land this in webkit sooner rather than later.

The front/back split should be relatively straight forward to pull off for the
scriptable API. I have some code in progress that I'll attach to the bug report
to demonstrate that part of things.

The front/back split for resource loading is less straight forward. I've been
working towards an impl for chromium in which the loading from an appCache
(including the loading of fallback resources) take place inside of
ResourceHandle from WebCore's point of view. I have not looked closely at how
to pull that part off on WebCore's side of the wire (so to speak).


-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.