From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <0644155cf9156095a99518f19429373d@terzarima.net>
From: Charles Forsyth <forsyth@terzarima.net>
Date: Wed, 15 Dec 2004 15:58:18 +0000
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Acme mailreader
In-Reply-To: <93455297-4EB0-11D9-901F-00112430C042@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Topicbox-Message-UUID: 17332e88-eace-11e9-9e20-41e7f4b1d025

>>Ah, I see. I'd hoped that acme could be persuaded simply
>>to read from ~/mail/inbox.mbox, and parse the messages

upas/fs centralises the parsing (and access to mail storage),
so that neither acme mail nor upas/nedmail need to do quite
as much parsing as most mail readers (for instance, upas/fs
deals with mime).  they don't touch the mailbox directly.
furthermore, by having upas/fs represent messages
including subcomponents as directories and subdirectories
in the name space, two different mail readers can be active
on the same mail box at once (with consistency enforced by upas/fs),
even across machine boundaries.