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

Re: FW: I-D ACTION:draft-dusseault-dav-quota-01.txt

From: Lisa Dusseault <lisa@xythos.com>
Date: Wed, 23 Oct 2002 09:55:56 -0700
To: "'Stefan Eissing'" <stefan.eissing@greenbytes.de>, "Webdav WG" <w3c-dist-auth@w3c.org>
Message-ID: <001001c27ab5$0ed451a0$620afea9@xythoslap>

Stefan asked (a while ago, sorry to be so late): 

> I can see how this draft is applied to servers like Sharemation
> which have a separate collection hierarchy for each user. 

Sharemation does have a separate collection hierarchy for each user, but
many other Xythos WebFile Server installations have users share
collections with common names like "sales", "marketing", "hr".  The same
quota system applies to both models, as I hope I'll be able to explain.

> I have more trouble applying it to servers where it is common 
> that more than one user has write access to collections. Imagine
> that Sharemation has a collection containing all your user
> collections. How would the quota properties appear on that
> collection?

Quota is applied to a collection, *not* a user, specifically because of
the model where a user doesn't just put documents in their own home
directory.  That's explicit in the draft, and it's an important feature
to allow directories to be shared by many users and still have quota
applied.  So if a quota of 1000MB is applied to the "/sales/"
collection, the server is free to report that quota, and count space
consumed by resources in the "/sales/" collection in whatever way its
policy decides.

> Where I see a real problem is a server supporting bindings.

It's specifically left up to the server to figure out how to support
bindings -- it would be impossible for the draft to enforce how to count
space used, when it's a matter of policy and the interaction of many
potential features.  The server may:
 - count the space used by a binding as 0 bytes, 
 - count the bytes used to store the binding only and not the length of
the resource it points to
 - divide the size of the target resource among all its bindings, 
 - count the full size of the target resource against every binding.
That's why the draft requires the server to show how space is used -- it
is not possible for the standard to decide these policy matters.

Received on Wednesday, 23 October 2002 12:56:11 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:01:27 UTC