W3C home > Mailing lists > Public > w3c-dist-auth@w3.org > January to March 2000

FW: [Moderator Action] RE: ETags

From: Jim Whitehead <ejw@ics.uci.edu>
Date: Thu, 17 Feb 2000 12:03:11 -0800
To: WebDAV WG <w3c-dist-auth@w3.org>
Accidentally caught by the spam filter.

- Jim

-----Original Message-----
From: Clemm, Geoff [mailto:gclemm@rational.com]
Sent: Wednesday, February 16, 2000 7:56 PM
To: w3c-dist-auth@w3.org
Subject: [Moderator Action] RE: ETags

A good reason to not change the etag or mod-date when a property changes
is that a property is often information about the resource, as opposed to
"being" the resource.  If I mark a resource as being "tested", I don't want
it to appear that the resource has changed (thus making it look like I need
to test it again).
A less compelling reason (but still a consideration) is to achieve
between dead and live properties.  You certainly don't want a change to the
"last access time" of a resource to modify the etag or "modification time"
that resource.
Add to this the fact that current implementations appear to not modify the
etag or
modification time when a dead property is modified, and I think we have a
case that neither the etag value nor the modification time should
be changed when a dead property is updated.


> -----Original Message-----
> From: Kevin Wiggen [mailto:wiggs@xythos.com]
> Sent: Wednesday, February 16, 2000 4:12 AM
> To: w3c-dist-auth@w3.org
> Subject: ETags
> I searched the spec and could not find any special details on handling
> ETags.
> Should an ETag value be updated when a dead property is 
> changed?  On the
> same note, do most servers update the last-modified-date when a dead
> property is changed?  Does Webdav want to take a stand one 
> way or another?
> Curious,
> Kevin
Received on Thursday, 17 February 2000 15:08:13 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:01:21 UTC