search

WICG / storage-buckets

API proposal for managing multiple storage buckets
https://wicg.github.io/storage-buckets/explainer
Other
44 stars 20 forks source link

delete vs clear #34

Open asakusuma opened 3 years ago

asakusuma commented 3 years ago

Similar to the questions posed in https://github.com/whatwg/storage/issues/88, would it be helpful to have a .clear() method (get rid of contents, but bucket remains) in addition to .delete()? As far as I can tell, this essentially boils down to: "do we want to be able to persist the bucket options/metadata even when the contents are deleted?"

evanstade commented 2 years ago

This line comes in handy again:

We want applications to be written assuming that each time they attempt to open a bucket, they may be creating the bucket from scratch.

(The reasoning here is that via automatic eviction or manual clear browsing data, the bucket could be deleted at any time and the app must expect that to happen.)

If authors are truly writing their code with this assumption, then they should always be specifying all the metadata about the bucket in the open call. If they do that, then there's little difference between clear and delete (just what's returned by the keys function between clear/delete and the next open). So I vote for no clear method.

evanstade commented 2 years ago

I guess the other difference would be what happens to the bucket or a storage type handle (such as the caches object) after delete() or clear() is called.