W3C home > Mailing lists > Public > whatwg@whatwg.org > February 2011

[whatwg] Intent of the FileSystem API

From: Charles Pritchard <chuck@jumis.com>
Date: Mon, 28 Feb 2011 14:54:15 -0800
Message-ID: <4D6C2797.3030100@jumis.com>
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?

-Charles
Received on Monday, 28 February 2011 14:54:15 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 16:59:31 UTC