From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: Re: Faster, lolcat. Faster!
Date: Thu, 02 Sep 2010 08:23:32 -0500 [thread overview]
Message-ID: <878w3k5lez.fsf@lifelogs.com> (raw)
In-Reply-To: <87lj7ke1pe.fsf@keller.adm.naquadah.org>
On Thu, 02 Sep 2010 15:04:29 +0200 Julien Danjou <julien@danjou.info> wrote:
JD> On Thu, Sep 02 2010, Ted Zlatanov wrote:
>> nnmaildir already does that. The problem is that Gnus flags are a
>> superset of what Maildir variants can handle.
JD> This is not a good reason to store *all* flags in a non-standard way.
Yes, of course. I didn't think I implied it was.
>> The nnmaildir slowness comes from its desire to be safe for access
>> from multiple machines to a shared spool. If it kept a message
>> database it would be much faster. The patches I mentioned were
>> discussed on emacs-devel move some of the message count tracking to
>> a single file, but it really needs to be a single file for flags and
>> counts. I asked Paul Jarc for comments on my proposal. See
>> http://thread.gmane.org/gmane.emacs.devel/125311/focus=126444 for
>> details. I think nnmaildir can be ridiculously fast for
>> single-client access if we allow it.
JD> That would be great, because I'm not sure that there's a point
JD> allowing multiple machine access from Gnus on Maildirs.
For shared filesystems like NFS it's extremely useful. I think that's a
small and shrinking proportion of Gnus users but we can't ignore them.
JD> Allowing multiple machine access to Maildir is a thing IMAP is good
JD> at.
s/IMAP is/IMAP servers are/ to be clear.
JD> On the other hand, I'm forced to use IMAP on *localhost* to access
JD> my Maildirs from Gnus, because Gnus does not cope correctly with
JD> Maildir.
Yeah. Whereas nnmaildir's problem is that it's slow, nnimap stores
flags in a server-specific way (no sharing of the spool), requires a
server to be running, has some issues with message counts, usually
requires authentication, etc. So we can't ask Gnus users to use it when
nnmaildir makes more sense.
Ted
next prev parent reply other threads:[~2010-09-02 13:23 UTC|newest]
Thread overview: 79+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-02 2:22 Lars Magne Ingebrigtsen
2010-09-02 2:41 ` Ted Zlatanov
2010-09-02 2:52 ` Lars Magne Ingebrigtsen
2010-09-02 4:48 ` Daniel Pittman
2010-09-02 14:26 ` Lars Magne Ingebrigtsen
2010-09-02 19:44 ` Russ Allbery
2010-09-02 5:20 ` David Engster
2010-09-02 14:15 ` Lars Magne Ingebrigtsen
2010-09-15 22:53 ` Tom Tromey
2010-09-02 7:29 ` Steinar Bang
2010-09-02 10:36 ` Ted Zlatanov
2010-09-02 11:10 ` Julien Danjou
2010-09-02 11:44 ` Frank Schmitt
2010-09-02 13:00 ` David Engster
2010-09-02 13:27 ` Ted Zlatanov
2010-09-02 14:23 ` Lars Magne Ingebrigtsen
2010-09-02 14:39 ` David Engster
2010-09-03 12:49 ` request-group-articles for nnimap (was: Faster, lolcat. Faster!) Ted Zlatanov
2010-09-03 18:10 ` request-group-articles for nnimap David Engster
2010-09-03 18:27 ` Lars Magne Ingebrigtsen
2010-09-07 15:45 ` Ted Zlatanov
2010-09-02 14:17 ` Faster, lolcat. Faster! Lars Magne Ingebrigtsen
2010-09-03 12:44 ` Ted Zlatanov
2010-09-03 13:08 ` Lars Magne Ingebrigtsen
2010-09-02 11:13 ` Julien Danjou
2010-09-02 12:44 ` Ted Zlatanov
2010-09-02 13:04 ` Julien Danjou
2010-09-02 13:15 ` Adam Sjøgren
2010-09-02 13:23 ` Ted Zlatanov [this message]
2010-09-02 13:25 ` Steinar Bang
2010-09-02 17:10 ` James Cloos
2010-09-03 16:59 ` Lars Magne Ingebrigtsen
2010-09-02 22:33 ` Romain Francoise
2010-09-03 17:01 ` Lars Magne Ingebrigtsen
2010-09-04 17:20 ` Lars Magne Ingebrigtsen
2010-09-04 17:57 ` Lars Magne Ingebrigtsen
2010-09-04 18:31 ` Adam Sjøgren
2010-09-04 18:34 ` Lars Magne Ingebrigtsen
2010-09-04 18:45 ` Adam Sjøgren
2010-09-04 18:48 ` Adam Sjøgren
2010-09-04 18:53 ` Lars Magne Ingebrigtsen
2010-09-04 21:30 ` Lars Magne Ingebrigtsen
2010-09-04 21:36 ` Lars Magne Ingebrigtsen
2010-09-04 21:57 ` Lars Magne Ingebrigtsen
2010-09-04 22:45 ` Lars Magne Ingebrigtsen
2010-09-04 22:50 ` Lars Magne Ingebrigtsen
2010-09-04 23:03 ` Adam Sjøgren
2010-09-05 0:19 ` Lars Magne Ingebrigtsen
2010-09-05 11:58 ` Adam Sjøgren
2010-09-05 9:10 ` Romain Francoise
2010-09-05 9:59 ` Steinar Bang
2010-09-05 9:06 ` Romain Francoise
2010-09-05 11:31 ` Lars Magne Ingebrigtsen
2010-09-05 12:44 ` Romain Francoise
2010-09-05 12:58 ` Lars Magne Ingebrigtsen
2010-09-04 18:50 ` Adam Sjøgren
2010-09-04 19:31 ` Adam Sjøgren
2010-09-04 19:49 ` Romain Francoise
2010-09-04 19:57 ` Lars Magne Ingebrigtsen
2010-09-04 20:08 ` Lars Magne Ingebrigtsen
2010-09-04 20:17 ` Lars Magne Ingebrigtsen
2010-09-04 22:01 ` James Cloos
2010-09-04 22:14 ` Lars Magne Ingebrigtsen
2010-09-05 21:25 ` James Cloos
2010-09-05 22:21 ` Lars Magne Ingebrigtsen
2010-09-06 19:05 ` James Cloos
2010-09-06 19:58 ` Lars Magne Ingebrigtsen
2010-09-05 22:41 ` Lars Magne Ingebrigtsen
2010-09-05 22:48 ` Lars Magne Ingebrigtsen
2010-09-04 23:10 ` Steinar Bang
2010-09-04 22:44 ` Romain Francoise
2010-09-04 22:47 ` Lars Magne Ingebrigtsen
2010-09-04 20:12 ` Adam Sjøgren
2010-09-04 22:16 ` Romain Francoise
2010-09-04 23:00 ` Lars Magne Ingebrigtsen
2010-09-05 8:59 ` Romain Francoise
2010-09-05 11:29 ` Lars Magne Ingebrigtsen
2010-09-04 22:37 ` Steinar Bang
2010-09-04 22:44 ` Lars Magne Ingebrigtsen
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=878w3k5lez.fsf@lifelogs.com \
--to=tzz@lifelogs.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).