- From: Eric Uhrhane via cvs-syncmail <cvsmail@w3.org>
- Date: Wed, 07 Mar 2012 22:55:00 +0000
- To: public-dap-commits@w3.org
Update of /sources/public/2009/dap/file-system
In directory hutz:/tmp/cvs-serv22561
Modified Files:
file-dir-sys.html
Log Message:
Remove obsolete issue, add small tweaks.
Index: file-dir-sys.html
===================================================================
RCS file: /sources/public/2009/dap/file-system/file-dir-sys.html,v
retrieving revision 1.42
retrieving revision 1.43
diff -u -d -r1.42 -r1.43
--- file-dir-sys.html 7 Mar 2012 22:47:17 -0000 1.42
+++ file-dir-sys.html 7 Mar 2012 22:54:58 -0000 1.43
@@ -242,12 +242,6 @@
the subsequent request SHOULD refer to the same underlying
filesystem and root directory as the previous request.</li>
</ul>
- <div class='issue'>
- <p>
- Do we need to mandate that the <a>temporary</a> and
- <a>persistent</a> filesystems be disjoint?
- </p>
- </div>
</section>
<section class='informative'>
<h2>Security Considerations</h2>
@@ -274,8 +268,9 @@
events.</li>
</ul>
This may be mitigated by restricting file creation/rename to
- non-executable extensions, and by making sure the execute bit is
- not set on any file created or modified via the API.
+ non-executable extensions, virtualizing paths [leading to
+ unguessable or non-executable filenames] and by making sure the
+ execute bit is not set on any file created or modified via the API.
</li>
</ul>
</p>
@@ -656,8 +651,7 @@
Proposal currently under discussion:
<ul>
<li>Use a format such as
- <code>filesystem:http://example.domain/persistent-or-temporary/path/to/file.html
- </code>.</li>
+ <code>filesystem:http://example.domain/persistent-or-temporary/path/to/file.html</code>.</li>
<li>URLs should be usable for anything that online URLs can be
used for, whether they appear in online or filesystem-resident
web pages.</li>
@@ -1042,7 +1036,7 @@
<code>err</code> parameter.
</p>
<dl class='parameters'>
- <dt>DOMError err</dt>
+ <dt><a>DOMError</a> err</dt>
<dd>
The error that was generated.
</dd>
@@ -1367,7 +1361,7 @@
<p>
If an error occurs while processing an asynchronous method,
the <code>err</code> argument to the <a>ErrorCallback</a> MUST
- be a <code>DOMError</code> object [[!DOM4]] of the most appropriate
+ be a <a>DOMError</a> object [[!DOM4]] of the most appropriate
type from the table below.
</p>
<h4>Error Descriptions</h4>
Received on Wednesday, 7 March 2012 22:55:02 UTC