With mail2fs I leave messages alone and use all kinds of mail lists
that contain just relative paths to actual messages. Perhaps nupas
could do the same.
El 09/06/2009, a las 20:11, quans...@quanstro.net escribió:
On Tue Jun 9 13:28:55 EDT 2009, mirtchov...@gmail.com wrote:
I think I've mentioned this before, but on a few of my synthetic file
systems here I'm using what you describe to slice a database by
specific orderings. For example, I have a (long) list of resources
which I'm managing in a particular environment each has an owner,
type, status and a few static data containers. It's all backed by a
relational database, but the file server presents different "slices"
of that to external users, where the directory structure is rigidly
defined [...]
this is definately a problem for upas/fs. it would be nice, for
example,
for upas/fs to have the option of sorting mailboxes in various ways.
imap4d's requirements are not the same as nedmail's. by thread,
by date, by order of arrival are all useful sortings. and of course,
given the ability to manage giant piles of messages reasonably
efficiently,
it's tempting to replace the idea of different boxes with different
views of the same giant pile of messages.
how are the resultant files looked up? it turns out that generating
the file hash table was the single most expensive operation for
upas/fs, given mailboxes with ~10k messages.
(http://9fans.net/archive/2009/05/106)
- erik
[/mail/box/nemo/msgs/200906/41850]
