W3C home > Mailing lists > Public > whatwg@whatwg.org > April 2017

Re: [whatwg] Accessing local files with JavaScript portably and securely

From: Anne van Kesteren <annevk@annevk.nl>
Date: Wed, 19 Apr 2017 11:28:32 +0200
Message-ID: <CADnb78hY6hpyDsbLkxcLUzLE-Rua6G5kW6L_q2MdJOizvHT30g@mail.gmail.com>
To: duanyao <duanyao@ustc.edu>
Cc: WHATWG <whatwg@lists.whatwg.org>, Ashley Sheridan <ash@ashleysheridan.co.uk>, Ian Hickson <ian@hixie.ch>, Roger H├ągensen <rh_whatwg@skuldwyrm.no>
On Wed, Apr 19, 2017 at 11:08 AM, duanyao <duanyao@ustc.edu> wrote:
> This is really not intended. I just don't quite understand some of those
> points. For example,
> Is "the web being fundamentally linked to HTTP" just the current status of
> the industry, or
> the inherent philosiphy of the web? If the latter, some explanation or
> document would be very
> appreciated.

I suspect it's actually a little higher-level than HTTP, with that
indeed being the current state, but the web is about the exchange of
data between computers and definitely sits at a higher level of
abstraction than the particulars of the Linux or Windows file system.
It's hard to define concretely I think, but being platform-independent
and having data addressable from anywhere are important principles.

> Doesn't file: protocol also abstract away much of the file system? What
> parts make it a bad abstraction?
> You mentioned casing and unicode normalization.

File URLs (it's not a protocol really) are still fundamentally tied to
the file system, including how it's hierarchical and such. And then
indeed there's all the legacy implications of file URLs.

> I'm not particularly eager to write access myself. Maybe we can seperately
> discuss read and write cases.

I already pointed to https://wicg.github.io/entries-api/ as a way to
get access to a directory of files and <input type=file> as a way to
get access to a sequence of files. Both for read access. I haven't
seen any interest to go beyond that.

Received on Wednesday, 19 April 2017 09:29:06 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 19 April 2017 09:29:07 UTC