W3C home > Mailing lists > Public > w3c-dist-auth@w3.org > October to December 2003

Re: Review of draft-ietf-webdav-quota-02.txt

From: Julian Reschke <julian.reschke@gmx.de>
Date: Sat, 13 Dec 2003 14:11:08 +0100
Message-ID: <3FDB0FEC.4000402@gmx.de>
To: WebDAV <w3c-dist-auth@w3.org>
Cc: Geoffrey M Clemm <geoffrey.clemm@us.ibm.com>

Just to restate, here are other issues that make the spec more 
complicated than it needs to be and/or incomplete:

- The spec tries to make handling of quotas simple by just reporting a 
single quota, selected by the server (just like in NFS). This is fine as 
long as the information is only used for display in the UI or for 
diagnostics. However, it fails completely if you want to make the quota 
authorable, because in this case you have no control whatsoever about 
*what* quota you're trying to change. I think this is the cause for most 
of the confusion about the "third" property. The simplest way to fix 
this is to remove support for authoring quota values from the spec.

- Disk limits are not quotas. Treating disk limits the same way causes 
funny effects. In addition, method failures due to physical storage 
limits should be treated differently (for instance, when mapping to a 
Unix FS like in the MacOS X driver, you may want to map to two separate 
error codes). IMHO the spec should clearly state that disk limits are 
*not* quotas. If it adds live properties and precondition/postcondition 
names to marshall to disk limit information *separately*, that'll be 
fine as well.

Regards, Julian

-- 
<green/>bytes GmbH -- http://www.greenbytes.de -- tel:+492512807760
Received on Saturday, 13 December 2003 08:12:05 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 2 June 2009 18:44:05 GMT