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: Julian Reschke <julian.reschke@gmx.de>
Date: Thu, 24 Oct 2002 13:56:01 +0200
To: "Stefan Eissing" <stefan.eissing@greenbytes.de>, <w3c-dist-auth@w3c.org>
Message-ID: <JIEGINCHMLABHJBIGKBCIEFPFKAA.julian.reschke@gmx.de>

> From: w3c-dist-auth-request@w3.org
> [mailto:w3c-dist-auth-request@w3.org]On Behalf Of Stefan Eissing
> Sent: Thursday, October 24, 2002 12:15 PM
> To: w3c-dist-auth@w3c.org
> Subject: Re: FW: I-D ACTION:draft-dusseault-dav-quota-01.txt
>
>
>
>
> Am Donnerstag, 24.10.02, um 00:25 Uhr (Europe/Berlin) schrieb Eric
> Sedlar:
>
> >
> >> - max. storage available to the user in quota-partition of the
> >> namespace
> > in
> >> which the collection is allocated
> >> - current storage allocated to the user in this partition
> >
> > Let's redefine the current draft to use these definitions--I'm happy
> > with
> > them, and I think they address Lisa's requirements as well.
>
> Agreed. Let's give it a try:
>
> quota space
>    A quota space is a storage area on a WebDAV server where the amount
>    of storage for resources is restricted. The restriction might be due to
>    physical disk size or limited by configuration options of the server.
>    The storage restriction might be enforced the same for all users,
letting
>    them share the available space, or configured and enforced differently
>    for each user.
>    A WebDAV collection belongs to at most one quota space. Subcollections
>    might belong to the same or different quota spaces.

If a subcollection can belong to a separate quota space (aka Unix device),
can't this also be the case for internal members?

I think that the distinction between collections and non-collections is
essentially meaningless -- the properties defined here apply to the quota
space, not to a particular resource. Therefore they should be defined on all
resources that are quota-controlled.

> (Comment: I'm not sure if we need identifier for quota spaces, so that
>   clients could compare if two collections are in the same quota.)

May be useful.

> A collection belonging to a quota space has the following two live
> properties:
>
> DAV:quota-free
>    The DAV:quota-free property reports the amount of storage in octets
>    available to the current user in the quota space the reporting
collection
>    belongs to.

...the reporting resource...

>    The value of this property will usually be protected, although a user
with
>     sufficient privileges may be permitted to change the value. The
>     property is useful even if it is protected. A 403 Forbidden response
>     is recommended for attempts to write a protected property.

Remove last two sentences.

>     A value of 0 indicates that storage is limited to 0.  Users will
>     probably not be able to add resources to the collection.

>     If a collection has no quota enforced, it should not return this
>     property at all.  A client cannot entirely assume that there is no
>     quota enforced on a collection that does not have this property, but
>     might as well act as if there is no quota.

Replace "should not return" by something like "MUST NOT be defined on the
resource".

>     This property is OPTIONAL on collections and SHOULD NOT exist on
>     non-collection resources.  When a new collection is created, it is
>     up to the server to initialize the value appropriately if it chooses
>     to.

Completely remove this paragraph.

> And
>
> DAV:quota-used
>    The DAV:quota-used property reports the amount of storage in octets
>    used by the current user in the quota space the reporting collection
>    belongs to.

... the reporting resource...

>   These values are an approximation and should be treated as such.
>    It is not required that DAV:quota-free and DAV:quota-used always add
up
>    to the same value.
>
>
>

Julian

--
<green/>bytes GmbH -- http://www.greenbytes.de -- tel:+492512807760
Received on Thursday, 24 October 2002 07:56:34 GMT

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