W3C home > Mailing lists > Public > public-script-coord@w3.org > July to September 2013

Re: Request for feedback: Filesystem API

From: Jonas Sicking <jonas@sicking.cc>
Date: Wed, 14 Aug 2013 00:03:06 -0700
Message-ID: <CA+c2ei_X6zwSRXoffYeQR20=8UJyNXLOKc+4AFYTWBJZjibibw@mail.gmail.com>
To: Brendan Eich <brendan@secure.meer.net>
Cc: Domenic Denicola <domenic@domenicdenicola.com>, public-script-coord@w3.org
On Aug 13, 2013 7:07 PM, "Brendan Eich" <brendan@secure.meer.net> wrote:
> Here's a particular question your comment prompts: Chrome's Filesystem
API, IIRC, was meant to map to files and directories that users could
rendezvous with via other tools, depending on the OS in question. Is this a
non-goal of the current webapps filesystem work?

That might have been a goal for Google early on, but implementation
experience made them give up on that goal. The differences between
different OS's requirements on filenames were to hairy to resolve.

So yeah, it is a non-goal of the Webapps sandboxes filesystem. Though
performance needs to match real filesystems. Which likely means that the
files needs to be stored as real files. Though with different names and
paths.

Once we expose real filesystems then obviously things are different. There
the paths and names will match those of real files. There we have no choice
but to tell authors "be careful about what names you use. And handle errors
gracefully!"

/ Jonas
Received on Wednesday, 14 August 2013 07:03:35 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:37:50 UTC