- From: Eric Uhrhane via cvs-syncmail <cvsmail@w3.org>
- Date: Fri, 11 Feb 2011 00:55:03 +0000
- To: public-dap-commits@w3.org
Update of /sources/public/2009/dap/file-system
In directory hutz:/tmp/cvs-serv4546
Modified Files:
file-dir-sys.html
Log Message:
Fix a number of error code values and descriptions, which got missed when I
updated to the new numbering system. Add a note about the proposed URI format.
Index: file-dir-sys.html
===================================================================
RCS file: /sources/public/2009/dap/file-system/file-dir-sys.html,v
retrieving revision 1.28
retrieving revision 1.29
diff -u -d -r1.28 -r1.29
--- file-dir-sys.html 19 Jan 2011 23:32:48 -0000 1.28
+++ file-dir-sys.html 11 Feb 2011 00:55:01 -0000 1.29
@@ -638,6 +638,24 @@
nice if these could be edited and manipulated easily, as with
normal filesystem paths.
</p>
+ <p>
+ How and where can these URIs be used? Can they be interchangeable
+ with online URIs for the same domain?
+ </p>
+ <p>
+ 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>
+ <li>URIs should be usable for anything that online URIs can be
+ used for, whether they appear in online or filesystem-resident
+ web pages.</li>
+ <li>However, they can only be used by the origin that owns the
+ filesystem. No other origin can e.g. reference another origin's
+ filesystem in an IMG tag.</li>
+ </ul>
+ </p>
</div>
</dd>
<dt>void remove ()</dt>
@@ -1565,23 +1583,30 @@
<tr><th>Name</th><th>Value</th><th>Description</th></tr>
</thead>
<tbody>
- <tr>
- <td>NO_MODIFICATION_ALLOWED_ERR</td><td>7</td>
- <td><a>user agent</a> MUST use this code when attempting to
- write to a file or directory which cannot be modified due to
- the state of the underlying filesystem.
+ </tr>
+ <td>ABORT_ERR</td><td>3</td>
+ <td>
+ This value MUST NOT be used in this API.
</td>
</tr>
<tr>
- <td>NOT_FOUND_ERR</td><td>8</td>
+ <td>ENCODING_ERR</td><td>5</td>
<td>
- <a>user agent</a> MUST use this code if a required file or
- directory could not be found at the time an operation was
- processed.
+ <a>user agent</a> MUST use this code when a URI supplied to
+ the API is malformed.
</td>
</tr>
<tr>
- <td>INVALID_STATE_ERR</td><td>11</td>
+ <td>INVALID_MODIFICATION_ERR</td><td>9</td>
+ <td>
+ <a>user agent</a> MAY use this code if the modification
+ requested is illegal. Examples of invalid modifications
+ include moving a directory into its own child or moving a file
+ into its parent directory without changing its name.
+ </td>
+ </tr>
+ <tr>
+ <td>INVALID_STATE_ERR</td><td>7</td>
<td>
<a>user agent</a> MAY use this code if an operation depends on
state cached in an interface object that has changed since it
@@ -1595,35 +1620,38 @@
</td>
</tr>
<tr>
- <td>INVALID_MODIFICATION_ERR</td><td>13</td>
+ <td>NOT_FOUND_ERR</td><td>1</td>
<td>
- <a>user agent</a> MAY use this code if the modification
- requested is illegal. Examples of invalid modifications
- include moving a directory into its own child or moving a file
- into its parent directory without changing its name.
+ <a>user agent</a> MUST use this code if a required file or
+ directory could not be found at the time an operation was
+ processed.
</td>
</tr>
<tr>
- <td>SECURITY_ERR</td><td>18</td>
+ <td>NOT_READABLE_ERR</td><td>4</td>
<td>
- <a>user agent</a> MAY use this code if:
- <ul>
- <li> it is determined that certain files are unsafe for
- access within a Web application</li>
- <li>it is determined that too many calls are being made on
- file resources</li>
- </ul>
- This is a security error code to be used in situations not
- covered by any other error codes.
+ <a>user agent</a> MUST use this code if a file or directory
+ cannot be read, typically due due to permission problems that
+ occur after a reference to a file has been acquired (e.g.
+ concurrent lock with another application).
</td>
</tr>
- <td>ABORT_ERR</td><td>20</td>
- <td>
- This value MUST NOT be used in this API.
+ <tr>
+ <td>NO_MODIFICATION_ALLOWED_ERR</td><td>6</td>
+ <td><a>user agent</a> MUST use this code when attempting to
+ write to a file or directory which cannot be modified due to
+ the state of the underlying filesystem.
+ </td>
+ </tr>
+ <tr>
+ <td>PATH_EXISTS_ERR</td><td>12</td>
+ <td><a>user agent</a> MUST use this code when failing to
+ create a file or directory due to the existence of a file or
+ directory with the same path.
</td>
</tr>
<tr>
- <td>QUOTA_EXCEEDED_ERR</td><td>22</td>
+ <td>QUOTA_EXCEEDED_ERR</td><td>10</td>
<td>
<a>user agent</a> MUST use this code if the operation failed
because it would cause the application to exceed its storage
@@ -1631,19 +1659,34 @@
</td>
</tr>
<tr>
- <td>NOT_READABLE_ERR</td><td>24</td>
+ <td>SECURITY_ERR</td><td>2</td>
<td>
- <a>user agent</a> MUST use this code if a file or directory
- cannot be read, typically due due to permission problems that
- occur after a reference to a file has been acquired (e.g.
- concurrent lock with another application).
+ <a>user agent</a> MAY use this code if:
+ <ul>
+ <li> it is determined that certain files are unsafe for
+ access within a Web application</li>
+ <li>it is determined that too many calls are being made on
+ file resources</li>
+ </ul>
+ This is a security error code to be used in situations not
+ covered by any other error codes.
</td>
</tr>
<tr>
- <td>ENCODING_ERR</td><td>26</td>
+ <td>SYNTAX_ERR</td><td>8</td>
<td>
- <a>user agent</a> MUST use this code when a URI supplied to
- the API is malformed.
+ This error code is not used in this specification; it is
+ included here only for completeness, as it is used in
+ [[!FILE-WRITER]].
+ </td>
+ </tr>
+ <tr>
+ <td>TYPE_MISMATCH_ERR</td><td>11</td>
+ <td>
+ <a>user agent</a> MUST use this code when the user has
+ attempted to look up a file or directory, but the Entry
+ found is of the wrong type [e.g. is a DirectoryEntry when the
+ user requested a FileEntry].
</td>
</tr>
</tbody>
Received on Friday, 11 February 2011 00:55:04 UTC