- From: Hartmut Warncke <hwarncke@Adobe.COM>
- Date: Mon, 04 Dec 2000 09:48:01 +0100
- To: Greg Stein <gstein@lyra.org>
- CC: w3c-dist-auth@w3.org
Greg, I think mod_dav is quite clean regarding that problem. But, for instance, IIS sends a status tag first and then a prop tag in a propstat although the DTD states: <!ELEMNENT propstat (prop, status, responsedescription?)> There are a few other samples like this one but I think the main problem is that the server and the client must be implemented in a way that they are able to handle requests and responses which are *not* correct regarding the DAV-DTD in RFC2518. I think the whole situation would be much easier and cleaner if clients and servers *must* use that DTD. Moreover it is maybe possible to get rid of some of the "ANY"s in that DTD. Best, Hartmut Greg Stein wrote: > On Fri, Dec 01, 2000 at 11:21:45AM +0100, Hartmut Warncke wrote: > >... > > I totally agree! If you look, for example, at implementations of RFC2518 you will > > come to the conclusion that a lot of problems of the "realworld" WebDAV client > > server communication are caused by the fact that a lot of clients and servers do > > *not* implement the DTD of RFC 2518 exactly because they don't have to. > > Do you have some examples of infractions like this? > > Or more close to home :-), have you seen any problems like this with mod_dav? > (because I'm unaware of them at this time, but would love to correct them if > they exist!) > > thx, > -g > > -- > Greg Stein, http://www.lyra.org/
Received on Monday, 4 December 2000 03:49:31 UTC