270
edits
MailNews:Better Faster IMAP Plan: Difference between revisions
→Implementation Plan
(→Tasks) |
|||
| Line 306: | Line 306: | ||
*** <i>Tagging an IMAP message</i>: 2 or 4 | *** <i>Tagging an IMAP message</i>: 2 or 4 | ||
*** <i>Selecting an IMAP folder</i>: 2 or 4 since header synchronization will be done on background - see following item | *** <i>Selecting an IMAP folder</i>: 2 or 4 since header synchronization will be done on background - see following item | ||
** Common | ** Common denominator of these states is 2, in other word, it is possible to cover every scenario for this feature by handling every IMAP operation as TB is in offline state. | ||
* Requirement #5 will be handled when #1 and #2 are implemented. Only additional requirement for this feature is to running COMPACTING operation automatically on mbox files to keep them slim. | * Requirement #5 will be handled when #1 and #2 are implemented. Only additional requirement for this feature is to running COMPACTING operation automatically on mbox files to keep them slim. | ||
* Requirement #6 requires creativity to keep the local database in sync with the server. Currently TB creates fake keys for the headers generated during an offline operation, and it replaces them (the headers) during the folder update. Possible solutions are: | * Requirement #6 requires creativity to keep the local database in sync with the server. Currently TB creates fake keys for the headers generated during an offline operation, and it replaces them (the headers) during the folder update. Possible solutions are: | ||