But we *do* have implementations -- Xythos WebFile Server and Apple
iDisk both implement quota with WebDAV properties to expose the values.
This implementation experience, and the desire to have interoperability
between the clients and servers from these two implementers, led to the
writing of the draft.
Thus, the draft is fairly reliably known to work for
- the Sharemation model, where every user is given a quota tied to
their home directory but they can assign sub-quotas to sub-directories
if they want
- the iDisk model, where every user is given a home directory and a
single top-level quota
- the WFS corporate customer model, where users put their stuff in
shared directories like 'dev', 'sales', 'hr' -- and so you can *only*
measure quota by directory, not by user.
We always have a temptation to make designs "more generally
applicable".. However sometimes I fear we fall in the trap of making the
designs too extensible, too theoretical, too much like a framework, and
in general too complex to actually reasonable accomplish what are
sometimes modest goals.
Lisa
> -----Original Message-----
> From: Eric Sedlar [mailto:eric.sedlar@oracle.com]
> You can't complain about not having implementations of the
draft--there's
> always
> a chicken & egg problem here.