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

> From: w3c-dist-auth-request@w3.org
> [mailto:w3c-dist-auth-request@w3.org]On Behalf Of Eric Sedlar
> Sent: Thursday, October 24, 2002 12:01 AM
> To: Julian Reschke; Lisa Dusseault; 'Webdav WG'
> Subject: Re: FW: I-D ACTION:draft-dusseault-dav-quota-01.txt
>
>
>
> > >
> > > All I want is for interoperable clients to have two properties:
> > >
> > > * how much junk can I store in this collection
> >
> > Yes.
> >
> > > * how much junk have I already stored in this collection (and
> thus could
> > be
> > > used if I delete stuff, potentially)
> >
> > That's hard to answer in the presence of bindings. It's certainly not a
> > property of a collection.
> >
>
> That's why I used the word "potentially".  It's just a way of giving the
user some
> indication of how much space could be usable in this collection  in the
best case
> (where any other space-occupying resources have been deleted).
>
> Certainly, if I have one collection mapping to D: and another mapping to
E: on
> a Windows machine, I would have different "used" quotas for different
collections.
> I don't see why it's not a collection property.

To compute it, you have to access collection and *all* descendants in the
namespace. So computing it may require the same amount of effort as doing a
PROPFIND with depth infinity. That's why I'd be very hesitant to consider it
being the property of a collection (yes, even taking the current allprop
semantics into account).

The things that *are* easy to answer for any resource (no matter whether
collection or plain resource) are:

- 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
- storage taken by *one* specific resource

Julian
--
<green/>bytes GmbH -- http://www.greenbytes.de -- tel:+492512807760

Received on Wednesday, 23 October 2002 18:09:49 UTC