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

["Thomas Broyer" <t.broyer@xxxxxxxxx>]

2006/11/16, Nikunj Mehta:
> Mark Baker wrote:
> > I don't quite follow, but idempotence just means that the effect of N
> > messages is the same as 1.
>
> 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.

app:edited might not be reflected in the "standalone" representation
of the entry (i.e. only shown in the "collection feed"); that way your
ETags might be the same.

...but an ETag might be computed based on the Last-Modified anyway, so...

> Doesn't that make this behavior *not* idempotent?

Whatever the answer to this question, I believe this has nothing to do
with the APP, it's all at the HTTP level (and how to interpret the
HTTP spec).

--
Thomas Broyer