Quoting Laurie Harper <[EMAIL PROTECTED]>:
> Remy Maucherat wrote:
> > The spec just states that principals can be resources if the
> > implementation choses to.
>
> Admittedly the language is a little vague, but my reading is that a
> principle is defined as an HTTP resource, and PROPFIND/PROPPATCH are
> optional.
>
> > That's not enough for me ... Perhaps I'll use one or two proprietary
> > properties to give role information, and manipultate that using
> > PROPPATCH/PROPFIND.
>
> Sounds like a better approach than defining custom methods :-)
Perhaps, but PROPPATCH/PROPFIND have to deal with a huge number of live
properties if you implement DAV ACL + Delta V. The XML document generated when
you do a PROPFIND/allprop on one resource is starting to get really big ;)
On the other hand, it would definitely be much better to go with something
really consistent with the specifications :-)
Remy
