Tickets :: Comment on [#11590] Kolab backend: IMAP cache does not get updated

* Your Email Address
* Spam protection	Enter the letters below: . .._.. ..___.. . \|_/ \| \|_/ _/ \|\/\| \| \_\|_\| \./__.\| \|
Comment	>>> I lack a final plan concerning the synchronization strategy. The >>> problem with the synchronization is that each list synchronization >>> costs two IMAP calls (LIST and METADATA) and each data >>> synchronization as well (STATUS and SEARCH - the latter identifies >>> deleted messages). >> >> Any reason you are not using CONDSTORE/QRESYNC if it is available? > > No. I planned to use these but never found the time to actually get > into this and write the necessary code. What you write sounds however > as if this would avoid even more IMAP calls than I expected. My > assumption was that CONDSTORE would allow me to reduce the two IMAP > calls in each situation to a single one. If there is even more to be > gained here then this makes implementing this even more attractive. > >> QRESYNC solves the last issue entirely (and CONDSTORE solves the last >> issue transparently within the Imap driver). However, a cache >> backend is needed to use these. >> >> Given the activesync may use MODSEQs also without using a cache >> driver, it may be useful to allow a MODSEQ to be explicitly given to >> the openMailbox command. Although this has major drawbacks, since >> openMailbox() is called extensively within the IMAP driver itself so >> a mailbox may already be open by the time a MODSEQ can be provided. >> >> A better option might be to create a custom cache driver to pass to >> the IMAP driver. >
Attachment
Watch this ticket

Saved Queries