Re: [bug-mailutils] POP3 code changes

[Sam Roberts]

Maildir doesn't really do locking, it avoids the need to lock at all
by modifying the status of messages (the only thing about a
message that is typically modified after delivery) not by modifying the
text of the message file, but by linking the message to a new file name,
with the status flags part of that file name.

I'd guess that mh and Maildir would share a lot of code, especially
the parts for reading messages, but the handling of the status flags,
and status updating, will be pretty different.

Cheers,
Sam

Quoteing address@hidden, on Mon, Dec 23, 2002 at 12:37:01PM -0800:
> On Mon, Dec 23, 2002 at 10:29:42PM +0200, Sergey Poznyakoff wrote:
> 
> > As I noticed before, the only difference between mh and maildir
> > is that the former does not make any provisions for locking
> > the particular message files, since mh is non-concurrent by its
> > nature, whereas maildir is. 
> 
> Is the locking harmful to MH?  I'm wondering if it might just be
> simplest to leave the locking in and unify the codebases completely. 
> That might also allow for crazy and unexpected uses of MH.  (Like a
> forgetful person starting something up in a second terminal at the same
> time as something is running in the first)
> 
> Tks,
> Jeff Bailey
> 
> 
> _______________________________________________
> Bug-mailutils mailing list
> address@hidden
> http://mail.gnu.org/mailman/listinfo/bug-mailutils