Re: Some problems with the WebDAV protocol

ylast@mindless.com wrote:

> > > So an HTTP/1.1
> > > client must interpret a 207 as being the same as a 200, although it clearly
> > > has a totally different meaning in WebDAV.
> >
> > I say again: it is not clear that the meaning is totally different.
>
> If it isn't different, then it would be OK to return a 200 response code
> to a WebDAV client in any event that only part of the collection had
> been deleted. Is that right?

No, that does not follow.

> > But it's pretty close to theoretical, because the client-side changes to switch from "do
> > a PUT and know that it'll create a collection" to "do a MKCOL followed by a PUT" are
> > trivial.
>
> And how do I do a MKCOL if I use Amaya, Netscape composer, AOLpress, etc.,...?

You can use a command-line utility for the (usually rare) occasons when you need it.

> > > Using DAV-like functionality of base HTTP/1.1 is one thing. Redefining that
> > > functionality is another.
> >
> > I assert again that we are not redefining anything; that the changes you see are totally
> > consistent with the HTTP/1.1 spec.
>
> If you make changes you are redefining (by definition).

No, we are extending.

> > No, by requiring special access rights for Depth=infinity.
>
> And when the request fails, how do you convey that to client?
> What status code will you use?

401, of course.

> How does that go along
> with:
> "DAV compliant servers MUST support the "0", "1" and "infinity" behaviors."

Support does not mean allow.

--
/=============================================================\
|John Stracke    | My opinions are my own | S/MIME & HTML OK  |
|francis@ecal.com|============================================|
|Chief Scientist | NT's lack of reliability is only surpassed |
|eCal Corp.      |  by its lack of scalability. -- John Kirch |
\=============================================================/

Received on Monday, 19 April 1999 13:36:36 UTC