- From: Greg Stein <gstein@lyra.org>
- Date: 1999年4月20日 01:13:46 -0700 (PDT)
- To: Henrik Frystyk Nielsen <frystyk@w3.org>
- cc: ejw@ics.uci.edu, w3c-dist-auth@w3.org
- Message-ID: <Pine.LNX.3.95.990420010940.32541A-100000@ns1.lyra.org>
On 1999年4月19日, Henrik Frystyk Nielsen wrote: > At 13:12 4/19/99 -0700, Jim Whitehead wrote: > >The rationale for the extra constraints on PUT in WebDAV is: > > > >* Prevention of creation of intermediate collections on user error. > > IMO, it seems out of bounce to impose a MUST requirement in order to > prevent a "user error" - especially because the "error" doesn't break > anything in the protocol or leads to interoperability problems. > > This is why it is stated as it is in HTTP/1.1 - it is left to the server to > decide whether it wants to create the new location or not. As Yoram points > out, some servers already do that and others don't. > > Removing the MUST requirement would also eliminate any problem with > HTTP/1.1 clients - removing their capability of creating resources is in my > mind not a good transition strategy. But since *some* servers do not create the intermediate collections (as you and Yoram have stated), isn't it a requirement that HTTP/1.1 clients need to somehow deal with them? Since they must deal with them, then why is it a problem that a certain subset of the servers they work against will exhibit this behavior? (those declaring Class 1 DAV conformance) Cheers, -g -- Greg Stein, http://www.lyra.org/
Received on Tuesday, 20 April 1999 04:15:45 UTC