|
Content-Type: |
TEXT/PLAIN; charset=US-ASCII |
Sender: |
|
Subject: |
|
From: |
|
Date: |
Mon, 3 Jan 2000 10:30:19 +0200 |
In-Reply-To: |
|
MIME-Version: |
1.0 |
Reply-To: |
|
With the extended usage of the WWW interface of Listserv for users and list
owners, I see more and more cases in which a command that takes a long time to
process (e.g a Search operation on a list with large archives, sometimes that
could take 2-4 minutes), postpones the response to a requests made at
the same time through the WWW interface.
In the days of e-mail transactions, that wasn't a problem,
because mail was essentially a 'batch' operation, but with the WWW interface,
which is more an on-line mode of operation, this is a problem.
I guess I am talking about Listserv being able to work in parallel..
Anything on that we can expect to in the future ?
Best,
Moshe
On Sat, 1 Jan 2000, Eric Thomas wrote:
> With the advent of the administrative web interface (as opposed to the
> browse-only web interface, which didn't need to issue LISTSERV commands),
> you're expected to take care of outgoing mail in a separate process.
> You can do this with the old ASYNCH_SMTP feature but I suggest
> using SMTP workers instead as this is more flexible. Just add something
> like:
>
> SMTP_FORWARD_1="2*my.smtp.server.com"
> export SMTP_FORWARD_1
>
> This creates 2 extra processes whose job is to clean up the outgoing
> spool directory. LISTSERV is then free to process commands as they
> arrive. Try it, it is night and day.
>
> Eric
>
|
|
|