W3C home > Mailing lists > Public > public-webapps@w3.org > October to December 2016

Re: A FileSystem API for the web

From: Feross Aboukhadijeh <feross@feross.org>
Date: Wed, 5 Oct 2016 21:41:15 -0700
Message-ID: <CA+nRABnPq=9C5QRULCKte3aWAJQie-tCMMMy-ZXUR1A3Tut6Qw@mail.gmail.com>
To: "public-webapps@w3.org" <public-webapps@w3.org>
Looks like there is also https://github.com/wicg/writable-files -- this
looks quite nice! What's the status of that spec?

Feross
Blog <http://feross.org/> | WebTorrent <https://webtorrent.io/> | Study
Notes <https://www.apstudynotes.org/>

On Wed, Oct 5, 2016 at 9:21 PM, Feross Aboukhadijeh <feross@feross.org>
wrote:

> The web really needs a proper filesystem to properly compete with native
> apps. I'd love to make WebTorrent (https://webtorrent.io) use the disk
> instead of in-memory storage, but there's no clear cross-browser solution.
> So, in the meantime, torrent data is stored in memory and lost when the
> user navigates to another page.
>
> Is there an active effort to make this happen? These are the specs I'm
> currently aware of:
>
> 1. File API (https://w3c.github.io/FileAPI/): widely implemented, 92%
> support
> 2. File API (Directories and System) (https://www.w3.org/TR/file-
> system-api/): Chrome only, deprecated, 51% support
> 3. FileSystem API (http://w3c.github.io/filesystem-api/): Meant to
> replace previous deprecated effort, Browser support unclear, spec status
> unclear to me
>
> Spec #1 is quite good, but it doesn't spec an entire filesystem. Spec #2
> would have been sufficient for our use case, but is deprecated. Spec #3
> seems like the best hope. Is that being worked on?
>
> Feross
> Blog <http://feross.org/> | WebTorrent <https://webtorrent.io/> | Study
> Notes <https://www.apstudynotes.org/>
>
Received on Thursday, 6 October 2016 04:42:24 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:15:04 UTC