- From: Andrew Sutherland <notifications@github.com>
- Date: Tue, 30 Jul 2019 10:51:14 -0700
- To: whatwg/storage <storage@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
- Message-ID: <whatwg/storage/issues/73/516523976@github.com>
The current Firefox/Gecko thinking here is: - (Versus storage pressure events) We strongly prefer exposing a mechanism to create multiple storage buckets to content where content can expose some eviction precedence. - Multiple buckets enables smaller quotas per bucket, including the default bucket. (Currently Gecko's default quota grant is overly generous.) - Multiple smaller buckets enables more granular eviction which should make it easier to ensure that we have the space available to fulfill the (smaller) quota that was promised to the origin. So most directly addressing the issue, in such a hypothetical future: - Gecko would claim there was quota space available even if there wasn't sufficient free disk space to back existing promises. - Gecko would evict not-currently-in-use buckets from other origins (and potentially the current origin) in order to make good on the quota. This might cause some (detectable) asynchronous write delays as eviction progresses in the pathological case, but ideally Gecko would maintain a working margin that avoids this. - Depending on how the multiple buckets spec shakes out, any live windows with live buckets open might be notified if their buckets were evicted out from under them, but otherwise origins would not be notified about their eviction. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/whatwg/storage/issues/73#issuecomment-516523976
Received on Tuesday, 30 July 2019 17:51:37 UTC