On 10 Oct 2013 11:23, "Spencer MacDonald" <[email protected]> wrote: > > The Purge API is something that I have been looking for, but the spec doesn't appear to have any way of finding out what messages have been purged from the archive, which means the local cache cannot be synced up with archive without fetching it all.
Astonishingly close to 5 years ago, I suggested that if we wanted to really have a generic archival sync protocol, we'd be best off just using IMAP. This is why. So removing random messages and then being able to later figure out which have been removed without storing buckets of state on the server is a hard problem. IMAP solves this by using eternally-unique ids that are numeric (and so collapse into ranges nicely, and are issued predictably), and deploying some fearsome logic, and allowing certain deletions to be re-transmitted. But it's hard - I think there's a good argument for moving any purging and resync to a different spec at least, and keeping MAM simple in scope. Dave.
