RE: FW: ETags again - basic question

Note that some file-based implementations store the dead properties as part
of the file content and use the file content information to compute the
etag.  So an interoperable client can only make the following assumptions:

- If the resource content changes, the strong etag MUST change.
- If the properties change, the strong etag MAY change.

Cheers,
Geoff 

-----Original Message-----
From: Jason Crawford [mailto:nn683849@smallcue.com]
Sent: Saturday, March 01, 2003 5:15 PM
To: Jim Whitehead
Cc: WebDAV
Subject: Re: FW: ETags again - basic question






Okay, I'll take a stab at this one...

> When does an (strong) etag of a resource change?
>
> 1) when the content of a resource has changed (e.g. after a PUT)
> 2) when one of the properties has changed (e.g. after a PROPPATCH)
> 3) in both cases 1) and 2)

I think the answer is whenever the GET response changes.  So for most
resources the answer is almost always (1), not (2) or (3).   If you have a
live
resource that is dependent on other info, the answer might vary.


------------------------------------------
Phone: 914-784-7569,   ccjason@us.ibm.com
I do not check nn621779@smallcue.com

Received on Sunday, 2 March 2003 08:48:21 UTC