- From: John Glavin <john@riverfrontsoftware.com>
- Date: Mon, 16 Apr 2001 17:00:14 -0700
- To: <w3c-dist-auth@w3c.org>
It doesn't really matter to me if the getlastmodified time can be written to as long as there is some mechanism in DAV for allowing 1) A time stamp property that gets updated by the server whenever the file contents are changed. I suppose it could be debated about what other changes to the file/properties might cause this property to change. 2) Allow the time stamp property to be modified by a client. John Glavin RiverFront Software john@webdrive.com http://www.webdrive.com ----- Original Message ----- From: "Jim Whitehead" <ejw@cse.ucsc.edu> To: "Jim Amsden" <jamsden@us.ibm.com>; <w3c-dist-auth@w3c.org> Sent: Monday, April 16, 2001 1:52 PM Subject: RE: WRITE_DAV_PROP: Summary of consensus > > > > getlastmodified needs to be updatable to do a UNIX-like touch > > command. Sets > > the modified date on a resource so dependent relationships are > > processed by > > builders or make. > > > > There are two choices for building - client side and server side. In client > side builds, the files are locally cached on client machine, and so the > existing "touch" command coul djust be used. > > For server-side builds, the existence of a rich property mechanism means > that we can do much better than the "touch" hack. > > This isn't a compelling scenario for me. > > - Jim
Received on Monday, 16 April 2001 19:50:09 UTC