MBOX-Line: From johngalton217 at gmail.com  Tue Mar 27 14:49:55 2012
To: imap-protocol@u.washington.edu
From: John Galton <johngalton217@gmail.com>
Date: Fri Jun  8 12:34:48 2018
Subject: [Imap-protocol] using a global CONDSTORE mod-sequence for
	HIGHESTMODSEQ
Message-ID: <CABHfyPTqCCkhERdbrZbix8zyqc=OjHPPCtcb0NeA4LdDhrnCww@mail.gmail.com>

The RFC states that the mod-sequence represents the highest modification to
a given mailbox.  If a mailstore only stored a global (account-wide, across
all mailboxes) mod-sequence, could one simply return the current value of
such a global mod-sequence when the HIGHESTMODSEQ is called for
(SELECT/EXAMINE/STATUS)?

Obviously using this value would trigger the client to followup with a
request to find out what has changed since it last sync'd, even if nothing
has changed.  Should a client be expected to behave reasonably if it's
FETCH CHANGEDSINCE or SEARCH MODSEQ returned items where the highest
mod-sequence was less than the advertised HIGHESTMODSEQ or worse, there
were no results at all when some were expected?

Thanks,
John
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman13.u.washington.edu/pipermail/imap-protocol/attachments/20120327/73270912/attachment.html>
