Re: Adding to configs
Tim Ellison OTT (Tim_Ellison@oti.com)
Wed, 22 Dec 1999 10:04:52 -0500
From: Tim_Ellison@oti.com (Tim Ellison OTT)
To: ietf-dav-versioning@w3.org ('Delta V')
Message-ID: <1999Dec22.100200.1250.1425537@otismtp.ott.oti.com>
Date: Wed, 22 Dec 1999 10:04:52 -0500
Subject: RE: Adding to configs
<jim>
I agree that with the semantics that Geoff describes for adding/removing
members from a configuration, but not the reuse of the LABEL method to do
so.
</jim>
Agreed.
<jim>
It might be better to use a CONFIGPATCH method with an XML request body
like PROPPATCH that has add/remove elements.
</jim>
I don't see any use for the property update body. I think the overloading
of that body format is not going to be useful here.
<jim>
But I like treating a configuration as a kind of collection and use
BIND/DELETE. To solve Tim's problem, we probably need to introduce a
Destination-Target-Selector
header.
</jim>
It's not _my_ problem, I just raised it!<g>
I also like your suggestion of a Destination-target-selector since I think
that we'll need that for COPY and MOVE.
I'd vote for BIND and DELETE rather than introducing a new method. The
collection semantics already assumes that the destination is overwritten if
it exists (we should also respect the overwrite flag in the header). This
seems intuative.
Tim