Gnus development mailing list
 help / color / mirror / Atom feed
From: Matt Armstrong <matt@lickey.com>
Subject: Re: nnmaildir.el + courier IMAP compatibility patch
Date: Fri, 03 May 2002 15:21:25 -0600	[thread overview]
Message-ID: <87d6wdylka.fsf@squeaker.lickey.com> (raw)
In-Reply-To: <m36625gi4l.fsf@multivac.cwru.edu> (prj@po.cwru.edu's message of "Fri, 03 May 2002 15:12:36 -0400")

prj@po.cwru.edu (Paul Jarc) writes:

> Matt Armstrong <matt@lickey.com> wrote:
>> prj@po.cwru.edu (Paul Jarc) writes:
>>> I've occasionally thought of writing an IMAP server that would store
>>> marks in an nnmaildir-compatible way.
>>
>> I've occasionally thought of going the opposite direction and forking
>> your nnmaildir.el to be less inode intensive by storing marks using
>> the "experimental suffix" method described in the maildir spec,
>
> That would save you one inode per group, at most.  (In my setup, it
> would save one inode total.)

I didn't realize the marks were hard links.  I've got plenty of inodes
to spare.

Anyway, the performance problems I was seeing went away when I set
gnus-fetch-old-headers to nil.  I had it set to 25.  I think
gnus-fetch-old-headers causes a lot of fetches by message-id.  Perhaps
that is slowish with nnmaildir?  I was seeing 30 second group entry
times for a group with 2500 messages, about 25 ticked and none of them
new.  That is gone now and it is pretty zippy.


>>> How does Courier store marks?
>>
>> With the maildir standard ":2,XYZ" suffixes on the filenames
>
> Ok.  There are a few reasons nnmaildir doesn't do that: it can't
> accommodate all of Gnus's marks; using two different storage methods
> for different sets of marks would be pretty ugly; treating the
> filename as constant makes concurrent use much easier.

First, lemme be clear that I think this is a minor thing and that
nnmaildir is great and I'm thankful that you created it.  :-)

But, do you worry about concurrent use by other email clients?  It
seems like nnmaildir can't depend on the :2, suffix remaining constant
anyway.

If that is the case, then the only implementation difficulty is
storing some marks one way and some marks another.  But abstracting
that behind an API doesn't seem too difficult.

One argument against the "maildir way" of storing marks is that it
makes it less efficient to, say, find all the ticked articles.  You've
got to glob the whole cur directory instead of just the ticked marks
dir.

But I still like it as a feature.  Say I go on vacation for two weeks
and read mail via a web mail client that accesses my mail via IMAP.
It'd be great to come back to Gnus and have everything I read actually
marked read in Gnus.  Maybe if I want this I should just read via IMAP
at all times -- I would if it weren't slower.


-- 
Don't send mail to Jan.Holm@hole.lickey.com
The address is there for spammers to harvest.



  reply	other threads:[~2002-05-03 21:21 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-02 17:39 Matt Armstrong
2002-05-02 22:32 ` Paul Jarc
2002-05-02 23:26   ` Lloyd Zusman
2002-05-03 16:41   ` Matt Armstrong
2002-05-03 17:19     ` Matt Armstrong
2002-05-03 17:53       ` Simon Josefsson
2002-05-03 21:01         ` Matt Armstrong
2002-05-03 19:12     ` Paul Jarc
2002-05-03 21:21       ` Matt Armstrong [this message]
2002-05-03 21:37         ` Paul Jarc

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=87d6wdylka.fsf@squeaker.lickey.com \
    --to=matt@lickey.com \
    /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).