MODSEQ in CONDSTORE

[Mark Crispin <mrc@xxxxxxxxxxxxxxxxxx>]

I know that it's probably much too late to complain about this now, but 
can someplace please explain why the MODSEQ is a 64-bit value?  Is there 
any serious possibility of there being more than 2^32 STOREs being 
performed on a single message in a mailbox?

The examples imply MODSEQ as a date/time, but as the document says you 
can't actually do that.

What's more, I didn't observe any definition in the CONDSTORE document of 
what is supposed to happen if a STORE results in no change.

I am implementing a new mailbox format which has a per-message 
modification sequence.  For my purpose, it's easiest to have it be 
monotonically increasing.  Also, I don't want to change it if STORE 
results in no change.  I was going to make this available as a MODSEQ for 
a possible future CONDSTORE implementation, but I see no point in keeping 
it as a 64-bit value other than bloating the data structures further. 
I want to see if I am missing something.

-- Mark --

http://panda.com/mrc
Democracy is two wolves and a sheep deciding what to eat for lunch.
Liberty is a well-armed sheep contesting the vote.