Re: Idempotent methods, HTTP PUT, and app:edited

[lawrence@xxxxxxxxx]

Sorry, I've lost some attributions here -- I think it was Nikunj who wrote:
> Exactly the point. When you see N different PUT requests, each
> produces a different app:edited (and hence a different ETag) value in
> the member entity. Doesn't that make this behavior *not* idempotent?

No it does not, because each PUT does not necessarily produce a
different app:edited -- because two *identical* PUT operations are NOT
an edit, q.e.d.  Idempotence can cut both ways.  

So, the responsibility just moved onto the poor implementor that a
series of subsequent PUT operations that are semantically equivalent
should not (SHOULD NOT?) count as an edit.

-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
	Lawrence Statton - lawrenabae@xxxxxxxxxxxxx s/aba/c/g
Computer  software  consists of  only  two  components: ones  and
zeros, in roughly equal proportions.   All that is required is to
sort them into the correct order.