imap - What modseq value to cache? -
I am reading, trying to figure out how a customer should behave when he Communicates with the server which is The case of the initial connection is fairly simple: the client compares its cash modal value to However, if the customer receives an unwanted This is difficult. The question probably refers to a language in RFC 716, which explains that In this special case where the server is only You should probably ask on the IPP protocol mailing list and get an explanation. I also have an open bug about how to handle it properly, and RFC is not quite clear to me. CONDSTORE but
QRESYNC not.
HIGHESTMODSEQ with the
select command, and if it is low , Then the customer can receive any change with
FETCH +
CHANGEDSINCE or
SEARCH +
MODSEQ . After doing this, the
HIGHESTMODSEQ value for the client mailbox can store its new cash modal value.
FETCH , responses when selecting a mailbox, does it contain any reliable findings from the
MODSEQ attributes in these updates Can it be removed? Will it be safe to cache the highest seen
MODSEQ value, or does the client take the risk of missing an update in the mailbox state to do so?
HIGHESTMODSEQ and
MODSEQ are two different animals, and one < code> FETCH MODSEQ , while a server is forced to withdraw some
EXPUNGE s, perhaps because the client sent a command MSN (see chapter 3.2) .
CONDSTORE and not
QRESYNC ,
MODSEQ and
HIGHESTMODSEQ is used only to track metadata changes (such as
flags updates). On expunges the message, they have to change not in which case RFC is trying to stop due to QRSENCN, without any fatal consequences, as you would like the customer No can use
HIGHESTMODSEQ for any other purpose, but on the basis of
Flags update, I do not see any reason that a customer will get the
See MODSEQ by
HIGHESTMODSEQ to
CONDSTORE on the server only And should not be. .
Comments
Post a Comment