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

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

From: Ashley Sheridan <ash@ashleysheridan.co.uk>
Date: Tue, 18 Apr 2017 10:52:10 +0000
To: whatwg@lists.whatwg.org, duanyao <duanyao@ustc.edu>, Roger H├ągensen <rh_whatwg@skuldwyrm.no>
Message-ID: <AA07F0C5-F0D7-4F8C-B9E4-259175C061ED@ashleysheridan.co.uk>


>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)


Thanks,
Ash
Received on Tuesday, 18 April 2017 10:52:43 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 18 April 2017 10:52:43 UTC