[Webkit-unassigned] [Bug 56704] New: [fileapi/chromium] Fetch platform path using GetMetadata before creating File from FileEntry*

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Fri Mar 18 21:16:29 PDT 2011


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

           Summary: [fileapi/chromium] Fetch platform path using
                    GetMetadata before creating File from FileEntry*
           Product: WebKit
           Version: 528+ (Nightly build)
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: HTML DOM
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: ericu at chromium.org
                CC: fishd at chromium.org, michaeln at google.com,
                    levin at chromium.org, kinuko at chromium.org


The implementation of the filesystem API currently requires that the embedder use real system paths for the underlying implementation.  This precludes implementations that e.g. use a database for underlying storage, in which case there aren't "real" platform paths for directories.

Chromium is about to switch to that type of implementation.  In order to make the WebCore parts portable, I'm going to switch all the cached platform paths to be filesystem URLs instead, as that's guaranteed to be portable.  However, when you create a File from a FileEntry, you need a real path to wherever the data's stored [unless you want to virtualize that too, but I'm not going to go that general until I know somebody actually needs it].

This change adds an alternative way to get the path, just for that call site.  Once this patch is in, I'll add the Chromium code that fills in the data, so it gets used.  Then I'll be able to do a cleanup pass [or 3], both removing the old code path and cleaning up the data types and variable names that refer to platform paths when they should refer to URLs.

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



More information about the webkit-unassigned mailing list