- From: John Glavin <john@riverfrontsoftware.com>
- Date: Fri, 13 Apr 2001 15:05:32 -0700
- To: "WebDAV WG" <w3c-dist-auth@w3.org>
I agree about the "getlastmodified" property. I would love to be able to set this so that file synchronization software will work properly. My product maps a network drive to a DAV server and unless I can set the "getlastmodified" property file synch software won't work right. I only know of one server that allows this now, it would be nice if this could be standardized. John Glavin RiverFront Software john@webdrive.com http://www.webdrive.com ----- Original Message ----- From: "Greg Stein" <gstein@lyra.org> To: "WebDAV WG" <w3c-dist-auth@w3.org> Sent: Friday, April 13, 2001 1:56 PM Subject: Re: Issue: WRITE_DAV_PROP > Seems fine, but... > > I could see an argument for getlastmodified (e.g. "touch" the resource). And > maybe for creationdate for somebody that is restoring documents to a server. > Then you have the "COPY is performed using PROPPATCH" where you may need to > copy all the props. > > I'm also a bit leery of the getcontentlanguage and getcontenttype being a > MUST. I'd prefer those be a MAY, and displayname and source remain as MUST. > The basic problem with the language/type is needing to look them up for each > GET from the server. That can seriously impact server performance. > > Cheers, > -g > > On Fri, Apr 13, 2001 at 09:02:25AM -0700, Kevin Wiggen wrote: > > > > I agree also. > > > > -----Original Message----- > > From: w3c-dist-auth-request@w3.org > > [mailto:w3c-dist-auth-request@w3.org]On Behalf Of Jim Whitehead > > Sent: Wednesday, April 11, 2001 9:53 AM > > To: WebDAV WG > > Subject: RE: Issue: WRITE_DAV_PROP > > > > > > I agree. > > > > - Jim > > > > > My vote: > > > - protected (i.e. properties that MUST NOT be modifiable with PROPPATCH) > > > creationdate > > > getcontentlength > > > getetag > > > getlastmodified > > > lockdiscovery > > > supportedlock > > > resourcetype > > > - not protected (i.e. properties that MUST be modifiable by PROPPATCH) > > > displayname > > > getcontentlanguage > > > getcontenttype > > > source > > > > > > My rationale for DAV:resourcetype is that the resourcetype should be used > > > to define the inherent nature of a resource (e.g. collection vs. > > > non-collection), while getcontenttype is definable by the client. > > > > > > Cheers, > > > Geoff > > > > > -- > Greg Stein, http://www.lyra.org/
Received on Friday, 13 April 2001 17:55:27 UTC