On Wed Sep 30 18:29:45 2009, Robin Collier wrote:
2 - That no two items published with the same item id can have the
same timestamp.
This takes care of the synchronization issue with regards to a
retrieve and notification
if an item has been replaced, since the combination of id and
timestamp now make
each instance of the item unique.
You're after something like RFC 2244's MODTIME, then? Something
that's *almost* a timestamp, but sacrifices accuracy for uniqueness
if needs must?
See http://tools.ietf.org/html/rfc2244#section-3.1.1 and its
description of the "modtime" attribute.
I think that's pretty much what you want. And I agree it's going to
be astonishingly rare that it's needed in normal cases, but I'm
mildly concerned that there's a possible timing attack lurking
somewhere if this is not mandated somewhere.
Dave.
--
Dave Cridland - mailto:[email protected] - xmpp:[email protected]
- acap://acap.dave.cridland.net/byowner/user/dwd/bookmarks/
- http://dave.cridland.net/
Infotrope Polymer - ACAP, IMAP, ESMTP, and Lemonade
