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

Why do you think this is preferable for the client?  Why not keep
single-property, single-value?  This complicates things even for the
server.

lisa

> -----Original Message-----
> From: Julian Reschke [mailto:julian.reschke@gmx.de]
> Sent: Thursday, October 24, 2002 10:31 AM
> To: w3c-dist-auth@w3c.org
> Subject: RE: FW: I-D ACTION:draft-dusseault-dav-quota-01.txt
> 
> 
> Here's a proposal for the property names that reduces property clutter
(by
> collapsing evrything into a single property) and possibly allows
> expressing
> multiple quota constraints:
> 
> <quota-set>
> 
>   <quota>
> 
>     <limit>...</limit>
>     <used>...</used>
> 
>     <!-- optional: identifies the principal this quota applies to -->
>     <principal><href>....</href></principal>
> 
>     <!-- optional: identifyer for quota-space -->
>     <qutoa-space><href>....</href></quota-space>
> 
>   </quota>
> 
>   <!-- more quotas, for instance for the current user group -->
>   ..
> 
> </quota-set>
> 
> The syntax is similar to lockdiscovery, so any self-respecting DAV
client
> should be able to handle this.
> 
> 
> --
> <green/>bytes GmbH -- http://www.greenbytes.de -- tel:+492512807760
>

Received on Thursday, 24 October 2002 14:21:55 UTC