Re: [whatwg] Storage Standard
Can't we use the permission API [1] for this? I.e. use the permission name persistent-storage or some such? So rather than default we're return prompt. [1] https://w3c.github.io/permissions/ / Jonas On Fri, May 1, 2015 at 5:11 AM, Anne van Kesteren ann...@annevk.nl wrote: Based on the discussion on this list and on: https://wiki.whatwg.org/wiki/Storage https://github.com/slightlyoff/StorageDurability Here's a first draft: https://storage.spec.whatwg.org/ https://github.com/whatwg/storage https://twitter.com/storagestandard It does not address multiple boxes for now. I hope we can continue discussing those in parallel, perhaps in the GitHub repository, as they are important to the gaming industry. Boxes can really help in the case where the site is trying to do the right thing and wants to avoid prompting the user, and also would allow introducing new global strategies such as an actual API-exposed cache (service workers' Cache API is all-or-nothing like any other API), or boxes with a max-age. -- https://annevankesteren.nl/
Re: [whatwg] Storage Standard
:) ! Is it ready to be spread? --- Delfi Ramirez My digital signature [6] +34 633 589231 del...@segonquart.net [7] twitter: delfinramirez IRC: segonquart Skype: segonquart [8] http://segonquart.net [9] http://delfiramirez.info [10] On 2015-05-01 14:11, Anne van Kesteren wrote: Based on the discussion on this list and on: https://wiki.whatwg.org/wiki/Storage [1] https://github.com/slightlyoff/StorageDurability [2] Here's a first draft: https://storage.spec.whatwg.org/ [3] https://github.com/whatwg/storage [4] https://twitter.com/storagestandard [5] It does not address multiple boxes for now. I hope we can continue discussing those in parallel, perhaps in the GitHub repository, as they are important to the gaming industry. Boxes can really help in the case where the site is trying to do the right thing and wants to avoid prompting the user, and also would allow introducing new global strategies such as an actual API-exposed cache (service workers' Cache API is all-or-nothing like any other API), or boxes with a max-age. Links: -- [1] https://wiki.whatwg.org/wiki/Storage [2] https://github.com/slightlyoff/StorageDurability [3] https://storage.spec.whatwg.org/ [4] https://github.com/whatwg/storage [5] https://twitter.com/storagestandard [6] http://delfiramirez.info/public/dr_public_key.asc [7] mail:%20del...@segonquart.net [8] skype:segonquart [9] http://segonquart.net [10] http://delfiramirez.info
[whatwg] Storage Standard
Based on the discussion on this list and on: https://wiki.whatwg.org/wiki/Storage https://github.com/slightlyoff/StorageDurability Here's a first draft: https://storage.spec.whatwg.org/ https://github.com/whatwg/storage https://twitter.com/storagestandard It does not address multiple boxes for now. I hope we can continue discussing those in parallel, perhaps in the GitHub repository, as they are important to the gaming industry. Boxes can really help in the case where the site is trying to do the right thing and wants to avoid prompting the user, and also would allow introducing new global strategies such as an actual API-exposed cache (service workers' Cache API is all-or-nothing like any other API), or boxes with a max-age. -- https://annevankesteren.nl/
