Gnus development mailing list
 help / color / mirror / Atom feed
From: "Jérôme Marant" <jerome.marant@fr.thalesgroup.com>
Subject: Re: Maildir backend
Date: Thu, 7 Mar 2002 09:56:42 +0100	[thread overview]
Message-ID: <20020307095642.A6244@fr.thalesgroup.com> (raw)
In-Reply-To: <m3k7spabu6.fsf@multivac.cwru.edu>; from prj@po.cwru.edu on Wed, Mar 06, 2002 at 11:40:27AM -0500

On Wed, Mar 06, 2002 at 11:40:27AM -0500, Paul Jarc wrote:
> Jérôme Marant <jerome.marant@fr.thalesgroup.com> wrote:
> >   I've tried nnmaildir but I think that it is not satisfactory
> >   since it takes a lot of resources (mostly heavy duplication of
> >   files)
> 
> What do you mean?

  I mean that it creates a .nnmaildir directory in the mail box
  directory. And it seems that all files from the cur directory
  are duplicated there. I would like the backend to avoid that
  duplication (even if I run a XFS filesystem).

> 
> >   it is pretty slow (the more files there are the slower
> >   it starts).
> 
> Yes, I've got some ideas to improve that.

  Avoid file duplication would be the first improvement I guess.

> 
> >   and renaming files with respect to their status (read,
> >   signed, and so on).
> 
> I don't think the standard maildir flags-in-filename scheme is
> sufficient to accomodate all of Gnus's marks (and certainly not
> user-defined marks).  We could have a different flags-in-filename
> scheme that would be more accomodating, but it would be unrecognizable
> to other maildir readers.  Would that still be worthwhile for you?
> What would be the advantages over nnmaildir's current mark system?

  I'm not that sure that a flags-in-filename scheme would be better.
  I'm not even waiting for any compatibility with other MUA.

  Why aren't directories new, cur and tmp plus a marks file (a kind
  of index file used to store the status of messages) enough to
  handle maildir ?

  Cheers,

-- 
Jérôme Marant



  reply	other threads:[~2002-03-07  8:56 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-06  9:31 Jérôme Marant
2002-03-06 16:40 ` Paul Jarc
2002-03-06 16:40 ` Paul Jarc
2002-03-07  8:56   ` Jérôme Marant [this message]
2002-03-07 18:00     ` Paul Jarc
2002-03-08 12:11       ` Jérôme Marant
2002-03-08 12:11       ` Jérôme Marant
2002-03-08 16:37         ` Paul Jarc
2002-03-08 16:37         ` Paul Jarc
2002-03-12  9:41           ` Jérôme Marant
2002-03-12 14:30             ` Paul Jarc
2002-03-13 10:51               ` Jérôme Marant
2002-03-13 16:26                 ` Paul Jarc
2002-03-13 17:33                   ` Matt Armstrong
2002-03-13 18:03                     ` Paul Jarc
2002-03-07 18:00     ` Paul Jarc
2002-03-07  8:56   ` Jérôme Marant
  -- strict thread matches above, loose matches on Subject: below --
2002-03-06  9:31 Jérôme Marant

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=20020307095642.A6244@fr.thalesgroup.com \
    --to=jerome.marant@fr.thalesgroup.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).