From: Simon Josefsson <sj@extundo.com>
Cc: Toby Speight <streapadair@gmx.net>,
The Gnus Mailing List <ding@gnus.org>
Subject: Re: mail split with multiple backends
Date: 26 Oct 2000 23:57:04 +0200 [thread overview]
Message-ID: <ilu1yx3feq7.fsf@barbar.josefsson.org> (raw)
In-Reply-To: <vafn1frz4fr.fsf@lucy.cs.uni-dortmund.de>
Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:
> > Quite a lot, I think, in the case of IMAP. AIUI, it uses IMAP's
> > move command while splitting - if it didn't, it would have to
> > download each article and upload it again.
>
> That's silly, of course. I think that all of Gnus could benefit from
> a faster move method. So why don't we add logic to Gnus which allows
> a faster move? The logic would take the source and target groups as
> input, then decide whether a fast move is possible, and invoke the
> fast move function as applicable.
This wouldn't help non-IMAP mail splitting since they don't use "move"
or "copy" at all, but rather "append". Which is good and fast for
nnmail-like backends. A backend independent splitter that used
backend optimizations where possible, with a user interface something
along the lines of
http://www.gnus.org/list-archives/ding/199901/msg00485.html
would be nice, and not very difficult, I think.
next prev parent reply other threads:[~2000-10-26 21:57 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-20 19:38 joules
2000-10-20 21:16 ` Kai Großjohann
2000-10-20 21:41 ` Rob Browning
2000-10-21 0:51 ` Harry Putnam
2000-10-21 4:45 ` Rob Browning
2000-10-21 11:09 ` Harry Putnam
2000-10-21 14:58 ` Rob Browning
2000-10-21 16:39 ` Kai Großjohann
2000-10-21 17:27 ` Rob Browning
2000-10-21 18:18 ` Kai Großjohann
2000-10-23 9:46 ` Didier Verna
2000-10-23 10:54 ` Kai Großjohann
2000-10-23 12:03 ` Didier Verna
2000-10-23 12:25 ` Kai Großjohann
2000-10-26 17:34 ` Toby Speight
2000-10-26 21:19 ` Kai Großjohann
2000-10-26 21:57 ` Simon Josefsson [this message]
2000-10-21 1:01 ` Harry Putnam
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=ilu1yx3feq7.fsf@barbar.josefsson.org \
--to=sj@extundo.com \
--cc=ding@gnus.org \
--cc=streapadair@gmx.net \
/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).