Re: [whatwg/storage] Storage container terms are mysteriously opaque (#101)

I'll comment to offer the context I have around buckets.

I think storage buckets are a relatively new concept in the realm of standards. Mozilla, LinkedIn and Google [presented a proposal](https://docs.google.com/presentation/d/143w70xtfqculs5x-bPgTOwu6GZO6uTOYeBjnN63pzs8/) at TPAC 2019. I think that @youennf attended [early discussions](https://docs.google.com/document/d/1eBWhY91nUfdT2mys3GaNKX4fKPei79Wk-KlWHYffbAA/).

Storage buckets first appeared as the TEMPORARY and PERSISTENT areas in the [file system API](https://dev.w3.org/2009/dap/file-system/file-dir-sys.html) that failed to gain cross-browser adoption and ended up as Chrome-only, and in [early Chrome-only iterations of the quota API](https://docs.google.com/document/d/19QemRTdIxYaJ4gkHYf2WWBNPbpuZQDNMpUVf8dQxj4U/edit#heading=h.t5z0x0uvm73k).

The current plan for adding buckets smoothly to the Web platform is to introduce a default bucket, and say that storage APIs have been using this default bucket all along. In Chrome, we'd say the TEMPORARY area is this default bucket.

I hope I've managed to give useful context and not add more confusion to this complex area :smile: 

-- 
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/101#issuecomment-643932020