My experience has been that if the server has a backlog of jobs to work on, the web interface dies.  This has been true in 1.8d and is still true in 1.8e.   If it got service between jobs it would be great.  A particular job is typically processed fairly quickly.

At 4:21 PM -0500 2/27/04, Francoise Becker wrote
>That is already how it works. Commands coming over the TCPGUI port by
>which the web interface interfaces with LISTSERV get highest
>priority. Of course if it's already busy with a mail command when the
>command comes in, it will finish that first.
>
>Francoise
>
>On 24 Feb 2004 at 11:08, Bill Verity <[log in to unmask]> wrote:
>
>> I believe when the server is backed up with incoming jobs the web
>> interface gets almost no service, by design.  I don't think this is
>> true with .mail files that are waiting to be delivered by smtp.  I
>> have no idea how the code works, but I believe it would be fine to
>> slow down the job flow to give the web interface better service.  My
>> rationale is that a person is waiting on the other end and once we
>> get them started they will sit there and think for a while so the
>> server can to back to working on jobs.  I'd rather give better
>> response time to the person at the expense of a little slower job
>> turnaround. What do you think?
>> --
>> A neutron goes into a bar and asks the bartender: How
>> much for a beer? The bartender replies: For you, no charge.
>>
>> Bill Verity - 814-865-4758  Fax: 814-863-7049
>> 215A Computer Building - Information Technology Services, Penn State University
>> At the office - on my Mac, of course ;-)


--
Cheerfulness is contagious, but don't wait to catch it from others. Be a "carrier".

Bill Verity - 814-865-4758  Fax: 814-863-7049
215A Computer Building - Information Technology Services, Penn State University
At the office - on my Mac, of course ;-)