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

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

From: duanyao <duanyao@ustc.edu>
Date: Tue, 18 Apr 2017 19:18:57 +0800
To: Ashley Sheridan <ash@ashleysheridan.co.uk>, whatwg@lists.whatwg.org, Roger Hågensen <rh_whatwg@skuldwyrm.no>
Message-ID: <17703d62-5faf-eb0a-ba2c-c6710d6c75a2@ustc.edu>
在 2017年04月18日 18:52, Ashley Sheridan 写道:
>> Maybe no. "files" is a generic word, so if you make every "xxx_files/"
>> folders magical, it's quite possible that there are folders happen to
>> ends with "_files" but are not intented to be local web apps. If you
>> require a `xxx.html` to make "xxx_files/" magical, it is a little
>> awkward and confusing for muli-page app.
>> This is why I propose a new (and unlikely already used) pattern
>> `xxx_webrun/` for more powerful muli-page app, and limit `xxx_files/`
>> to
>> single page app.
>> In single page app case, it would be more common that `test.html` gets
>> `test_files\page{2|3}.html` via XHR and renders the latter in place,
>> instead of navigating to it.
>> So the latter don't need to access `test_files\config.json` themselves.
> *any* magic behavior is a sure-fire sign that something is wrong(TM)
Maybe. But there are occasions where magic is unavoidable. E.g. how to 
infer the MIME type of a file? filename extension? magic numbers? all 
are magic.

If the barrier is not high enough, name it `xxx__webrun__/`.

> Thanks,
> Ash
Received on Tuesday, 18 April 2017 11:20:35 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 17:00:42 UTC