From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: To: 9fans@cse.psu.edu Subject: Re: [9fans] Scaleable mail repositories. From: "Fco. J. Ballesteros" Date: Mon, 31 Oct 2005 12:32:10 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Topicbox-Message-UUID: a32219b6-ead0-11e9-9d60-3106f5b1d025 It's easy to write file servers, but that does not mean that it's the right way to proceed. IMHO, if you want to see your mail as files, and you have a file server, it's easier to store the mail in that format. All the code necessary to handle your storage and index structure becomes fossil/venti, and all that has to be done is to convert from the mbox format into your preferred archival format, and to feed upas with input messages for sending. Isn't this more simple and powerful? Or are you thinking of something else that is best done using the existing format? : i don't understand why, now that it's easy to write file servers : (compared to unix days), it's necessary to store the mail messages : as actual separate files or directories. the main problem with : upas/fs i find is that it rewrites the file instead of treating it : as append-only, and it reads the whole thing into memory (in a moderately : bulky format); rather than maintaining a separate index file or files, : and loading as needed. both the storage and index structure can : then be made suitable for the task.