9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Fco. J. Ballesteros" <nemo@lsub.org>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Scaleable mail repositories.
Date: Mon, 31 Oct 2005 12:32:10 +0100	[thread overview]
Message-ID: <c00ae94f2710029fd8649a092b77590d@lsub.org> (raw)

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.



             reply	other threads:[~2005-10-31 11:32 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-31 11:32 Fco. J. Ballesteros [this message]
2005-10-31 16:01 ` Ronald G Minnich
2005-10-31 15:06   ` jmk
  -- strict thread matches above, loose matches on Subject: below --
2005-11-09  9:45 Fco. J. Ballesteros
2005-11-09 10:24 ` Charles Forsyth
2005-11-09 14:19   ` Sam
2005-11-10  1:24     ` erik quanstrom
2005-11-10  2:30       ` Russ Cox
2005-11-10  6:33         ` Scott Schwartz
2005-11-10 11:55         ` erik quanstrom
2005-10-31 15:33 Fco. J. Ballesteros
2005-10-31 18:38 ` William Josephson
2005-10-31 15:19 Fco. J. Ballesteros
2005-10-31 15:14 Fco. J. Ballesteros
2005-10-31 16:22 ` Ronald G Minnich
2005-10-31 18:37   ` William Josephson
2005-10-30  1:10 [9fans] rfork(RFPROC) and ffork() geoff
2005-10-30  1:18 ` Paul Lalonde
2005-10-31  4:06   ` [9fans] Scaleable mail repositories Lyndon Nerenberg
2005-10-31 10:55     ` C H Forsyth
2005-10-31 12:32       ` erik quanstrom
2005-11-01 19:56         ` rog
2005-11-01 22:29           ` Francisco J Ballesteros
2005-11-08 19:56             ` rog
2005-11-08 23:22               ` Joel Salomon
2005-11-09  0:51               ` Caerwyn Jones
2005-11-09  0:55                 ` Russ Cox
2005-11-09  3:32               ` erik quanstrom
2005-10-31 15:30       ` jmk

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=c00ae94f2710029fd8649a092b77590d@lsub.org \
    --to=nemo@lsub.org \
    --cc=9fans@cse.psu.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).