[Webkit-unassigned] [Bug 41637] Web Inspector: Give Semantics to "Refresh" and "Delete" Buttons in ApplicationCache DataGrid

[bugzilla-daemon at webkit.org]

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





--- Comment #13 from Joseph Pecoraro <joepeck at webkit.org>  2010-07-09 13:46:23 PST ---
> Not a bug... WebKit's impl holds all resources in memory for caches that are in use,
> so documents that are associated will still be able to access those resources even
> after makeObsolete has done its work.

Oh. Thanks for that explanation!


> Chrome's impl doesn't hold everything in memory so when a group is made obsolete
> we can't delete the resource data from disk. Equating this delete function to making
> a group obsolete is close but not quite right.

Okay. Well, in either case, when to delete something from disk sounds like an
implementation detail. I think from a user standpoint, the action they would want to
perform is "make this cache group obsolete" and how the implementation handles
things (deleting from disk or not) is not the user's concern. In Chromium's case, that
can be something you can choose to do.

For a potential user who develops using ApplicationCache, they aren't concerned
with the implementation details. They only know what the spec says, and to them
making something "obsolete" is itself a concrete action. I don't think they would
understand "make obsolete and delete from disk", because to them that is invisible.
This is just like your suggestion for "Refresh" to be action "update and swapUpdate",
that is a concrete action in high level application cache terms, not implementation
details.


> After doing this, sub resource loads in all pages associated with any cache from
> that group will fail.

To me this sounds like a very small drawback to the Chromium delete approach.
But, its certainly in no way harmful.

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