From: Simon Josefsson <jas@extundo.com>
Cc: ding <ding@gnus.org>
Subject: Re: nnimap slow for message copy
Date: Sat, 27 Apr 2002 00:25:03 +0200 [thread overview]
Message-ID: <ilusn5it7wg.fsf@extundo.com> (raw)
In-Reply-To: <vqopu0mjpv0.fsf@astazou.imag.fr> (Nicolas Kowalski's message of "Fri, 26 Apr 2002 20:07:15 +0200")
Nicolas Kowalski <Nicolas.Kowalski@imag.fr> writes:
> Simon Josefsson <jas@extundo.com> writes:
>
>> The problem is that the Gnus backend interface doesn't use COPY when
>> copying something, I think, so it ends up using fetch+store. Of course,
>> the nnimap backend could detect this situation and use COPY instead. (As
>> it does when moving messages, I think.)
>
> Hm, reading nnimap.el (line 1294), I see :
>
> (deffoo nnimap-request-accept-article (group &optional server last)
> (when (nnimap-possibly-change-server server)
> (let (uid)
> (if (setq uid
> (if (string= nnimap-current-server nnimap-current-move-server)
> ;; moving article within same server, speed it up...
> (and (nnimap-possibly-change-group
> nnimap-current-move-group)
> (imap-message-copy (number-to-string
> nnimap-current-move-article)
> group 'dontcreate nil
> nnimap-server-buffer))
>
>
> So the optimization already exists...
Yes, but only used when moving articles. I guess the details could be
set when copying articles too?
> I simply do not understand what this function is supposed to do, nor
> how to use it with a group-to-group copy.
Look at `nnimap-request-move-article'. Setting the same details from
`nnimap-request-article' could work.
prev parent reply other threads:[~2002-04-26 22:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-26 13:40 Nicolas Kowalski
2002-04-26 17:23 ` Simon Josefsson
2002-04-26 17:50 ` Jody Klymak
2002-04-26 18:07 ` Nicolas Kowalski
2002-04-26 22:25 ` Simon Josefsson [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ilusn5it7wg.fsf@extundo.com \
--to=jas@extundo.com \
--cc=ding@gnus.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).