W3C home > Mailing lists > Public > public-webapps@w3.org > January to March 2011

Re: [whatwg] Intent of the FileSystem API

From: Charles Pritchard <chuck@jumis.com>
Date: Mon, 28 Feb 2011 15:50:35 -0800
Message-ID: <4D6C34CB.8080309@jumis.com>
To: public-webapps@w3.org
On 2/28/2011 3:50 PM, Ian Hickson wrote:
> On Mon, 28 Feb 2011, Charles Pritchard wrote:
>> I'd like some clarification on the intent of the FileSystem API:
>> requestFileSystem permanent, getDirectory and getFile.
>>
>> Are they intended to directly pass through to the host operating system, or
>> are they just programming constructs?
>>
>> They're not particularly easy to use, compared to the IndexedDB data store,
>> but if they are OS level commands,
>> then they do help with usability of a web app with the rest of the OS: with
>> managing files directly from the OS file manager.
>>
>> Is the FileSystem API intended to expose a folder on the host operating
>> system, or is it just an abstraction
>> which can be bolted onto any data system (such as, using SQLite as a backend,
>> as appCache and IndexedDB do)  ?
>>
>> Are there any plans of reviewing/visiting efficient File/Blob support in
>> indexeddb?
> You are likely to get a more useful response to your questions if you send
> the above feedback to the lists mentioned in the specs as the place to
> send feedback, namely public-webapps@w3.org:
>
> | If you wish to make comments regarding this document, please send them
> | to public-webapps@w3.org (subscribe, archives).
>   -- http://dev.w3.org/2009/dap/file-system/file-dir-sys.html
>   -- http://dvcs.w3.org/hg/IndexedDB/raw-file/tip/Overview.html
>
> HTH,
Received on Monday, 28 February 2011 23:51:15 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:43 GMT