From: nobody@nowhere.invalid (Unknown)
Cc: joseph@cis.ohio-state.edu
Subject: Re: External delivery: Pros and cons
Date: Sun, 20 Oct 2002 20:13:53 +0000 (UTC) [thread overview]
Message-ID: <9638.53962389312$1042179050@news.gmane.org> (raw)
X-Geek-3: GE/CS d+(--) s:++>: a C++++$ ULUHO++++$ P+++$ L+++ E+++
W+++$ N+++ K-? !w--- O-? !M-- !V-- PS+ PE- Y+ PGP++ t@ 5++ !X R++
b+++ DI+++ D- G e+++ h+ r++ y+
X-Face: #q.#]5@vq!Jz+E0t_/;Y^gTjR\T^"B'fbeuVGiyKrvbfKJl!^e|e:iu(kJ6c|QYB57LP*|t&YlP~HF/=h:GA6o6W@I#deQL-%#.6]!z:6Cj0kd#4]>*D,|0djf'CVlXkI,>aV4\}?d_KEqsN{Nnt778"OsbQ["56/!nisvyB/uA5Q.{)gm6?q.j71ww.>b9b]-sG8zNt%KkIa>xWg&1VcjZk[hBQ>]j~`WqXl,y1a!(>6`UM{~'X[Y_,Bv+}=L\SS*mA8=s;!=O`ja|@PEzb&i0}Qp,`Z\:6:OmRi*
X-Organization: University of Massachusetts, Amherst, MA 01003
X-Time: Fri Nov 17 04:40:49 1995
X-Mail-System: Vm 5.95 (beta) for GNU Emacs 19.14 XEmacs Lucid (beta5)
References: <199511151538.HAA00082@edmonds.home.cs.ubc.ca>
From: Manoj Srivastava <srivasta@pilgrim.umass.edu>
Date: 17 Nov 1995 04:40:48 -0500
In-Reply-To: Brian Edmonds's message of Wed, 15 Nov 1995 07:38:25 -0800
Message-ID: <gvxbuqbh93z.fsf@plymouth.pilgrim.umass.edu>
Organization: Project Pilgrim, University of Massachusetts at Amherst
Lines: 42
X-Mailer: September Gnus v0.14
Hi,
>>"Brian" == Brian Edmonds <edmonds@cs.ubc.ca> writes:
Date> 15 Nov 1995 03:01:39 -0500
>>
Cons>
Brian> One con you forgot that used to bother me a lot: when you
Brian> filter incoming messages, you end up with one (potentially
Brian> large: perl) process per message. If you're on a system like
Brian> mine where I retrieve mail via UUCP once per hour, all those
Brian> processes starting up at once can put a serious strain on the
Brian> system. I have blown out my virtual space once in the past
Brian> when I was only running with 20M.
If you use mailagent as your external splitting agent, then
the filtering is two phased, each mail message invokes a small filter
written in C, that spools the files locally, and calls the
(potentially large) perl mailagent just once for a batch of files. I
think it would solve your problem with batch downloads (works great
for me on a linux box).
Brian> I find splitting the mail inside emacs is pretty quick, unless
Brian> you've got hundreds of messages, and far kinder on my hard
Brian> drive and system performance. As it is, just punting
Brian> everything through sendmail at once produces a noticable lag.
Well, I need mailagent for other things, and did not feel like
maintaining two sets of filtering rules.
Brian> Brian. http://www.cs.ubc.ca/spider/edmonds
manoj
-- Burnt Sienna. That's the best thing that ever happened to
Crayolas. Ken Weaver
Manoj Srivastava Project Pilgrim, Department of Computer Science
Phone: (413) 545-3918 A143B Lederle Graduate Research Center
Fax: (413) 545-1249 University of Massachusetts, Amherst, MA 01003
email:srivasta@pilgrim.umass.edu http://www.pilgrim.umass.edu/~srivasta/
next reply other threads:[~2002-10-20 20:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-20 20:13 Unknown [this message]
-- strict thread matches above, loose matches on Subject: below --
1995-11-15 8:01 Sudish Joseph
1995-11-15 15:38 ` Brian Edmonds
1995-11-16 4:37 ` Scott Blachowicz
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='9638.53962389312$1042179050@news.gmane.org' \
--to=nobody@nowhere.invalid \
--cc=joseph@cis.ohio-state.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).