[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Nmh-workers] Future directions for nmh
From: |
Lyndon Nerenberg |
Subject: |
Re: [Nmh-workers] Future directions for nmh |
Date: |
Wed, 16 Mar 2016 13:58:04 -0700 |
> On Mar 11, 2016, at 9:09 PM, Ken Hornstein <address@hidden> wrote:
>
> There was a guy on this mailing list who's name escapes me right now ...
> who was a real bear when it came to insisting that nmh should stick to
> 100% POSIX compatibility. You should talk to him. What was his name
> again ....?
Oh bite me! :-)
You know this sort of thing falls well outside POSIX. It would be inside a
non-portability #ifdef.
But if you want me to get all pedantic, I could write a protocol interface,
spoken through a named socket - which is POSIX portable - through which anyone
could write their own message store interface adapters as external interfaces.
Actually, that's my preferred scheme. But it's not trivial to do – on either
side – so FUSE seemed like a more practical solution.
--lyndon
- Re: [Nmh-workers] Future directions for nmh, (continued)
- Re: [Nmh-workers] Future directions for nmh, Laura Creighton, 2016/03/11
- Re: [Nmh-workers] Future directions for nmh, David Levine, 2016/03/12
- Re: [Nmh-workers] Future directions for nmh, Ken Hornstein, 2016/03/11
- Re: [Nmh-workers] Future directions for nmh, Jon Steinhart, 2016/03/11
- Re: [Nmh-workers] Future directions for nmh, Lyndon Nerenberg, 2016/03/11
- Re: [Nmh-workers] Future directions for nmh, Ken Hornstein, 2016/03/12
- Re: [Nmh-workers] Future directions for nmh,
Lyndon Nerenberg <=
- Re: [Nmh-workers] Future directions for nmh, Ken Hornstein, 2016/03/16
- Re: [Nmh-workers] Future directions for nmh, Lyndon Nerenberg, 2016/03/16
- Re: [Nmh-workers] Future directions for nmh, Ken Hornstein, 2016/03/16
- Re: [Nmh-workers] Future directions for nmh, Lyndon Nerenberg, 2016/03/16
- Re: [Nmh-workers] Future directions for nmh, Paul Vixie, 2016/03/16
- Re: [Nmh-workers] Future directions for nmh, Lyndon Nerenberg, 2016/03/16
- Re: [Nmh-workers] Future directions for nmh, Paul Vixie, 2016/03/16
- Re: [Nmh-workers] Future directions for nmh, Ken Hornstein, 2016/03/16
- Re: [Nmh-workers] Future directions for nmh, chad brown, 2016/03/17
- Message not available
- Re: [Nmh-workers] Future directions for nmh, Conrad Hughes, 2016/03/16