From: Charles Forsyth <forsyth@terzarima.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Scaleable mail repositories.
Date: Wed, 9 Nov 2005 10:24:55 +0000 [thread overview]
Message-ID: <57471c9f2e6b9a4c77886fffb87d244d@terzarima.net> (raw)
In-Reply-To: <449538154806c7a7e62a2519f277faf6@lsub.org>
> It would have to be triggered on the changing of files in the
> file system. With some help from the fs, this becomes cheap.
i myself don't want the mail system to have to rely on a particular
underlying file system. you could certainly push an indexing fs in front
of any other, i suppose, but relying on there being a
definite article (`the' file system), as that and similar remarks
imply, doesn't seem right to me in a distributed system where
different filing resources can be bound in on demand.
next prev parent reply other threads:[~2005-11-09 10:24 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-09 9:45 Fco. J. Ballesteros
2005-11-09 10:24 ` Charles Forsyth [this message]
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
-- strict thread matches above, loose matches on Subject: below --
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-31 11:32 Fco. J. Ballesteros
2005-10-31 16:01 ` Ronald G Minnich
2005-10-31 15:06 ` jmk
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=57471c9f2e6b9a4c77886fffb87d244d@terzarima.net \
--to=forsyth@terzarima.net \
--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).