MBOX-Line: From dkarp at zimbra.com  Mon Jun 14 13:28:11 2010
To: imap-protocol@u.washington.edu
From: Dan Karp <dkarp@zimbra.com>
Date: Fri Jun  8 12:34:44 2018
Subject: [Imap-protocol] IMAP MOVE extension
In-Reply-To: <alpine.OSX.2.00.1006141208460.662@hsinghsing.panda.com>
Message-ID: <915336234.3135.1276547291546.JavaMail.root@dogfood.zimbra.com>

> Thus, the server benefit, such as it is, is for some database type
> store which can not do a basic-level operation quickly but can do
> an extended operation quickly.

Note that the discussion is not MOVE vs. COPY, but actually between
MOVE vs. COPY/STORE/EXPUNGE.  Which, in such a database-based store,
would likely be one UPDATE vs. one INSERT, one UPDATE, and one
DELETE.

In addition, you could posit a store where the searchable message
content (for SEARCH BODY, etc.) is shared among all copies of a 
message.  In such a store, once a COPY was performed you'd end up
in a more expensive ref-counting mode for subsequent deletes of
copied messages, a mode avoided in the absence of a COPY op.

