Summary: | [Chromium] Mods for a chrome specific impl of ApplicationCacheHost | ||||||
---|---|---|---|---|---|---|---|
Product: | WebKit | Reporter: | Michael Nordman <michaeln> | ||||
Component: | WebCore Misc. | Assignee: | Jeremy Orlow <jorlow> | ||||
Status: | RESOLVED FIXED | ||||||
Severity: | Normal | CC: | fishd, jorlow | ||||
Priority: | P2 | ||||||
Version: | 528+ (Nightly build) | ||||||
Hardware: | Other | ||||||
OS: | OS X 10.5 | ||||||
Attachments: |
|
Description
Michael Nordman
2009-08-07 16:54:05 PDT
Created attachment 34348 [details]
use PLATFORM(CHROMIUM) to segregate the private section
Fyi: I've intentionally chosen to use the PLATFORM flag here to help clarify what parts of the appcache system are actually in the CHROMIUM port. The majority of the appcache directory is not, a few files are... * ApplicationCacheHost.h * DOMApplicationCache.idl .h .cpp Using the PLATFORM() flag in this .h file is reflective of that, and while it may not make it crystal clear what classes/files are relevant to CHROMIUM, it does provide big clues that ApplicationCacheGroup and familiy don't apply. My thinking is that having this reflected in the .h file helps with maintainability. I'd be willing to shuffle some more deck chairs around to create a ApplicationCacheHostInternal class that inter-operates with ApplicationCacheGroup and family (and removes the PLATFORM flag), but for the reason stated above, I don't think that would be an improvement. Will land by hand in a sec. Sending WebCore/ChangeLog Sending WebCore/loader/appcache/ApplicationCacheHost.cpp Sending WebCore/loader/appcache/ApplicationCacheHost.h Sending WebCore/page/DOMWindow.cpp Transmitting file data .... Committed revision 47018. http://trac.webkit.org/changeset/47018 |