Re: [Jmap] Draft messages - mutability

["Chris Newman" <[e-mail]>]

On 24 Apr 2017, at 18:35, Neil Jenkins wrote:
> On Tue, 25 Apr 2017, at 11:02 AM, Chris Newman wrote:
>> I see a lot of cost and no benefit to making a draft a different
>> datatype from a message.
>
> I don't see any benefit to making it a different data type. However,
> what we currently have is that, like IMAP, a message is immutable 
> except
> for flags/mailboxes. This is a pain for client authors trying to keep
> track of a single draft as it is saved through multiple revisions
> (especially when the user has multiple clients). One possible solution
> to this is to simply say any message with the \Draft flag set is fully
> mutable (while keeping the same id). I think we would also want the
> server to enforce that a message cannot be changed from/to draft state
> after creation. If it starts a draft it stays a draft, or vice versa.

Why is it important to keep the same ID when modifying a draft? The 
approach draft-brandt-imap-replace uses is to include the new ID in the 
response to the modification operation. The replace model seems a good 
way to preserve the immutable property (which is very helpful for quick 
synchronization) while providing the client an interface that looks just 
like editing an existing message.

		- Chris