Re: [quota-api] Rethink about the storage model (#2)

@sicking
> The big thing that have changed in my thinking since we last worked on the quota API is that I think that we should make it so that when a website requests persistent storage, and the user grants that, that it should change the storage policy for all data currently stored by that website.

Yeah I basically agree with this, or I've started to feel the same.  Setting a per-origin quota limit was ok but asking apps to set the amount wasn't really practical, and requiring changes for storage APIs to use persistent storage was blocking us from going further.  So origin's default storage mode could be either temporary (best-effort) or persistent, and to use the storage in the default mode no special API or syntax is required-- sounds simple.

A few things we could do in this spec for that direction would be:
* Deprecate `requestPersistentQuota(bytes)`
* Instead add `requestStorageDurability()` or something similar. (Or at least make quota API work with the new API if it wants to be in a separate spec)
* Also maybe add a storage type "default" and make `queryInfo("default")` (or just `queryInfo()` without parameter) return the origin's current storage situation with its default storage mode.  (This way it would still give modest backward compatibility for old API users, i.e. FileSystem API users)

---
Reply to this email directly or view it on GitHub:
https://github.com/w3c/quota-api/issues/2#issuecomment-90882444