- From: Jonas Sicking <jonas@sicking.cc>
- Date: Thu, 3 Feb 2011 16:33:10 -0800
- To: Joćo Eiras <joao.eiras@gmail.com>
- Cc: public-webapps@w3.org
On Thu, Feb 3, 2011 at 3:59 PM, Joćo Eiras <joao.eiras@gmail.com> wrote: > >>> Before storing X amount of data with an API, the code requests enough >>> space for the storage area that API covers. That's how I understand >>> the use case. Then it's up to the user agent to communicate that >>> appropriately to the user, if applicable. >> >> Why would we need to have the app specify "I want to store 5MB in >> indexedDB and 3MB in the FileSystem"? The user won't care; at most, >> the user needs to know "This app wants to use up 8MB of space". If >> the user doesn't care, why make the app make two requests? > > Because the user agent needs to differentiate which api will use each quota. I think the idea with this spec is that it *requires* that implementations share quota between its various storage mechanisms. As an implementor I think this is a good idea. / Jonas
Received on Friday, 4 February 2011 00:34:04 UTC