Re: Why MD5 Headers are Imperative

On 17/8/06 5:28 PM, "Eric J. Bowman" 
<eric-MkmoNbc1SAncr/OS1auqaA@xxxxxxxxxxxxxxxx> wrote:

>> I do agree that id+updated doesn't make a very good ETag, so why don't
>> you assign something better?
>> 
> 
> What I'm saying is that id+updated makes a _perfectly_ good eTag, if I wasn't
> trying to implement APP alongside it what would be wrong with it?  Please
> don't make Atom Format implementers break their cache strategy in order to
> support the Atom Publishing Protocol.

Just for a moment lets pretend that atom:updated was actually atom:urgent (a
string data type, indicating the degree of urgency the publisher thinks the
consumer of the content should assign to the entry) ... would id+urgent make
a _perfectly_ good eTag?

No. It's a subjective qualification of the content, intended to be
interpreted and acted on by the reader of the content, not the publisher of
the content.

atom:updated has the same characteristics, and is at least equally
inadequate.

e.