Sync Newest Messages First

Registered by Daniel Fore on 2010-11-14

When Postler syncs for the very first time, it can take a while before the client is actually usable due to the sync order. In order to work around mbsync's method of syncing the oldest messages first, on Postler's first sync there should be a loop that goes something like this:

MaxMessages = n
n = 1
while there are unsynced messages on the server {
sync
n = n + 10
}
n = 0

We would use the "MaxMessages" option in the mbsyncrc file to accomplish this. We would need to know the number of messages on the server so that once that number was reached, we could set "MaxMessages" back to 0 (unlimited). We would also need to run the sync again and again in quick succession until that was reached, at which point it could go back to the standard 10 minute interval.

This should be a decent work around that will make Postler usable more quickly and then revert to the previous behavior once it is no longer necessary.

Blueprint information

Status:
Not started
Approver:
None
Priority:
Undefined
Drafter:
Daniel Fore
Direction:
Needs approval
Assignee:
None
Definition:
New
Series goal:
None
Implementation:
Unknown
Milestone target:
None

Related branches

Sprints

Whiteboard

Also, it's important to note, that this would only work on the first sync, if you set the max to below the number of messages you actually have, it starts deleting them.

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.