Re: IMAP article move

[David Abrahams <dave@boost-consulting.com>]

Simon Josefsson wrote:
> "Ted Zlatanov" <tzz@lifelogs.com> writes:
> 
>> Can we optimize IMAP article moves so they use the server
>> capabilities?  Right now, I think, we just copy and then delete the
>> old article.  Across various backends that makes sense, but if it's
>> within the same IMAP backend, the server move can be much faster.
>>
>> I looked at gnus-sum.el, gnus-int.el, and nnimap.el.  It seems
>> possible, although the changes would have to go all the way to the
>> top, because gnus-summary-move-article does the copy & delete action.
>>
>> If this works, Gnus will be much faster and more reliable in the
>> common case of article moves in IMAP.
> 
> What are you proposing?  There is some optimization in
> nnimap-request-move-article and nnimap-request-accept-article to make
> moving more efficient, and I thought it was pretty fast.  But I rarely
> copy/move articles, so I wouldn't know.  Maybe you could illustrate by
> comparing which IMAP commands are sent now, and which commands you
> want to be sent?

The thing that seems to hurt usability the most for me is that Gnus
rebuilds the summary buffer after each message is moved in a
multiple-message move.

-- 
Dave Abrahams
Boost Consulting
http://www.boost-consulting.com