Re: [Jmap] Draft messages - mutability

[Ted Lemon <[e-mail]>]

That seems okay as long as there isn't a ton of churn in the drafts folder.

On Apr 24, 2017 10:18 PM, "Neil Jenkins" <[e-mail]> wrote:

> On Tue, 25 Apr 2017, at 12:00 PM, Ted Lemon wrote:
>
> If drafts are mutable, the implication is that synchronization based on
> message ID can't happen without something like a version modifier. At which
> point why not make every message versioned?
>
>
> I'm not sure I fully understand your question; every message is already
> versioned (like the IMAP CONDSTORE modseq) so that you can efficiently
> synchronise changes.
>
> There is a well-defined model of data synchronisation which is used across
> all data types in JMAP. A client can request the list of ids of a type
> (let's say Messages) which have changed since the client's current state.
> It can then decide which of those messages it wants to fetch, and what
> information it needs to fetch for each one. In the case of non-drafts, it
> only needs to fetch flags/mailboxes. If drafts are mutable, then for any
> draft message it has it would need to redownload the entire message. This
> is the trade-off I was talking about in my previous post.
>
> Neil.
>