Re: [imap5] ERASE command as part of MOVE

Bron Gondwana <brong@fastmail.fm> Sat, 02 June 2012 04:24 UTC

Date: Sat, 02 Jun 2012 06:24:09 +0200
From: Bron Gondwana <brong@fastmail.fm>
To: Barry Leiba <barryleiba@computer.org>
Message-ID: <20120602042409.GC2654@launde.brong.net>
References: <20120601222311.GB598@launde.brong.net> <CAC4RtVBrM2fY7GGM1s-NRhKMU48NSOMMtkMVqnQ_zbbLnBtM_A@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <CAC4RtVBrM2fY7GGM1s-NRhKMU48NSOMMtkMVqnQ_zbbLnBtM_A@mail.gmail.com>
Organization: brong.net
User-Agent: Mutt/1.5.21 (2010-09-15)
Cc: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>, imap5@ietf.org
Subject: Re: [imap5] ERASE command as part of MOVE
Precedence: list

On Fri, Jun 01, 2012 at 09:54:54PM -0400, Barry Leiba wrote:
> As Timo says, you can pipeline the STORE and UID EXPUNGE.  Unless you
> can come up with some reason that an atomic ERASE command would save
> something significant in the message store -- something I can't
> imagine to be the case -- there's nowhere near the use for this as
> there is for MOVE (where it's not just the round trips that are saved,
> because it allows message-store optimization in some cases).

OK, a REAL atomic erase (no intermediate state - guaranteed) gives you
this:

S1: UID MOVE 1:* FolderA
S2: UID MOVE 1:* FolderB

A guarantee that at the end, the messages will be in FolderA OR FolderB,
but not in both.

Bron.

[imap5] ERASE command as part of MOVE Bron Gondwana
Re: [imap5] ERASE command as part of MOVE Timo Sirainen
Re: [imap5] ERASE command as part of MOVE Barry Leiba
Re: [imap5] ERASE command as part of MOVE Bron Gondwana
Re: [imap5] ERASE command as part of MOVE Bron Gondwana
Re: [imap5] ERASE command as part of MOVE Bron Gondwana
Re: [imap5] ERASE command as part of MOVE Arnt Gulbrandsen
Re: [imap5] ERASE command as part of MOVE Bron Gondwana
Re: [imap5] ERASE command as part of MOVE Timo Sirainen