From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <3bd9fd157a7ee4567da63233405e130e@quanstro.net>
To: 9fans@9fans.net
From: erik quanstrom <quanstro@quanstro.net>
Date: Thu, 12 Jun 2008 10:25:20 -0400
In-Reply-To: <8ccc8ba40806120703k5849a853t869a3eefe2ba309f@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Subject: Re: [9fans] store 9p session-only values using lib9p
Topicbox-Message-UUID: bdb3849c-ead3-11e9-9d60-3106f5b1d025

> If, the reply was inlined. Anyone wanting to use the original can go use raw.
> But the nice thing is that you can edit text, copy attachments in/out,
> remove them, etc. etc.

this is already possible with upas/fs, isn't it?  also, i get the benefit
of not being tied into message formats.  for example, i can use imap.

in addition, doesn't storing mail your way increase the storage requirements?
also, what do you do about header parsing without upas/fs's help?

(storing small mailboxes as a mdir even consumes more resources than
a mbox.  unfortunately, i have to account for massive mail boxes.)

> Compatibility in my case is achieved by leaving upas et al. as they
> are; I convert
> just my mail once it entered the system.

mboxes are the single biggest resource pig we have.  we comfortably
did development on a single pIII fs with a single ide disk and 256mb
of memory before email was treated as the great repository of all
human knowledge.

so my primary goal is to have mail use as few resources as
reasonablly possible.

- erik