My reading of the HTTP/1.1 spec (specifically 3.11 [1] and 13.3.3 [2])
says that an ETag (Entity Tag) is attached to a representation rather
than a resource. In particular:
An entity tag MUST be unique across all versions of all
entities associated with a particular resource. (3.11)
and:
The entity tag MAY be used for comparison with other entities
from the same resource. (13.3.3)
...which says to me that I should generate the tag based on the content
of a representation. Does this sound right?
FWIW: this is what I did in the sample app, but I didn't document why.
Which means I forgot it within days...
Chris
[1] http://www.w3.org/Protocols/rfc2616/rfc2616-sec3.html#sec3.11
[2] http://www.w3.org/Protocols/rfc2616/rfc2616-sec13.html#sec13.3.3
--
Chris Winters ([EMAIL PROTECTED])
Lead Software Developer
Vocollect Healthcare Systems
CONFIDENTIAL, PRIVILEGED COMMUNICATION: This e-mail is private and
intended for the addressee(s) only. It may contain privileged and/or
confidential information. If you have received it in error you are not
authorized to disseminate it in any manner; please delete it and any
copies and reply to the sender that it was misdirected.
