[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [bug-mailutils] POP3 code changes
From: |
Alain Magloire |
Subject: |
Re: [bug-mailutils] POP3 code changes |
Date: |
Mon, 23 Dec 2002 16:12:00 -0500 (EST) |
>
> > This was more a question for Sergey, is MH cleanly separated ?
>
> Oh, sorry for having replied late... Well, yes it is clearly separated
> in the sense that it follows the current mailutils paradigm, that is
>
> 1) it is concentrated in the three files: mbx_mh.c, folder_mh.c and
> url_mh.c;
Yes, to be accessible in the mailutils framework i.e.
mailbox_create() etc ..
So any application could understand MH __whithout__ changing the code
# frm mh://home/alain/Mail
or something similar.
But, could it be separate, for application that __only__
want to build with MH and link whith only mh support, the opposite of
the mailutils framework 8-).
#include <mailutils/sys/mh.h>
int main() {
..
mh_get_sequence(mh, &seq) // MH functions API
..
}
The challenge of mailutils/mailbox2/* was a few things:
(1) one more layer beetween mailbox_t and the implementation
so they both could be use independently.
(2) Better C OO model to allow cleaner subclass
(3) maybe drop supports for non-blocking and thread-safe
...
I think we can start merging back or get the work in mailutils/mailbox
for the point (1).
The problem with (2) is that I do not have enough time to take
this up and it will mean long breakage.
So, let's do this by iterations 8-), longer but things can still
be tested and release.
> 2) these sources do not depend on other sources, except
> "*0.h" headers;
>
> 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. Thus, most of the mh functions should
> work for maildir except deleting and appending. The straight method
> of joining the two functionalities (mh and maildir), would be to
> add the locking to mbx_mh.c, leaving it disabled by default for pure
> mh and enabled ny default for maildir. Then, we would need a common
> header file for mbx_mh.c and mbx_maildir.c. I'll try to implement
> this during the holidays.
>
> Regards,
> Sergey
>
>
>
> _______________________________________________
> Bug-mailutils mailing list
> address@hidden
> http://mail.gnu.org/mailman/listinfo/bug-mailutils
>
--
au revoir, alain
----
Aussi haut que l'on soit assis, on est toujours assis que sur son cul !!!
- Re: [bug-mailutils] POP3 code changes, (continued)
- Re: [bug-mailutils] POP3 code changes, Sergey Poznyakoff, 2002/12/23
- Re: [bug-mailutils] POP3 code changes, Jeff Bailey, 2002/12/23
- Re: [bug-mailutils] POP3 code changes, Sergey Poznyakoff, 2002/12/23
- Re: [bug-mailutils] POP3 code changes, Jeff Bailey, 2002/12/23
- Re: [bug-mailutils] POP3 code changes, Sergey Poznyakoff, 2002/12/23
- [bug-mailutils] mailutils todo, Alain Magloire, 2002/12/23
- Re: [bug-mailutils] POP3 code changes, Sam Roberts, 2002/12/25
- Re: [bug-mailutils] POP3 code changes, Jeff Bailey, 2002/12/23
- Re: [bug-mailutils] POP3 code changes, Sergey Poznyakoff, 2002/12/23
- Re: [bug-mailutils] POP3 code changes, Jeff Bailey, 2002/12/23
- Re: [bug-mailutils] POP3 code changes,
Alain Magloire <=
- Message not available
- Re: [bug-mailutils] POP3 code changes, Jeff Bailey, 2002/12/23
- Re: [bug-mailutils] POP3 code changes, Sergey Poznyakoff, 2002/12/23
- Re: [bug-mailutils] POP3 code changes, Alain Magloire, 2002/12/23
- Message not available
- Re: [bug-mailutils] POP3 code changes, Jeff Bailey, 2002/12/23
- Re: [bug-mailutils] POP3 code changes, Alain Magloire, 2002/12/23
- Message not available
- Re: [bug-mailutils] POP3 code changes, Jeff Bailey, 2002/12/23