Eric J. Bowman schrieb:
...
If the purpose of an Atom Publishing Protocol is to interface with Atom-
format documents which uniquely allow this divergence then some method other
than HTTP cache-control must be used to determine whether the Member resource
has been edited on the back-end in a way which has not changed its cached
representation. What we need is some method to implement a "validated miss"
which doesn't ivalidate requests (which may not have the purpose of editing)
for the Member resource, but which serves an undeniably fresh editable
representation to APP clients, while preventing the lost-update problem.
...
Eric,
I'm not sure what problem you're trying to solve. It seems that you're
saying that the current HTTP machinery, using Last-Modified, Etag,
Cache-Control and so on is insufficient. Could you give a concrete
example for that? In particular, why isn't a string ETag sufficient, and
if it isn't, why doesn't that cause problems in WebDAV as well?
Best regards, Julian
