Re: Communciator 4.02 Imap EXPUNGE problem

"Barry Leiba, Multimedia Messaging" <leiba@watson.ibm.com> Mon, 25 August 1997 19:54 UTC

Received: from cnri by ietf.org id aa18245; 25 Aug 97 15:54 EDT
Received: from lists3.u.washington.edu (root@lists3.u.washington.edu [140.142.56.3]) by cnri.reston.va.us (8.8.5/8.7.3) with ESMTPid PAA04210 for <ietf-archive@CNRI.Reston.VA.US>; Mon, 25 Aug 1997 15:57:46 -0400 (EDT)
Received: from host (lists.u.washington.edu [140.142.56.13]) by lists3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id MAA25656; Mon, 25 Aug 1997 12:54:24 -0700
Received: from mx3.u.washington.edu (mx3.u.washington.edu [140.142.13.230]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id MAB33294 for <imap@lists.u.washington.edu>; Mon, 25 Aug 1997 12:51:33 -0700
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mx3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.04) with ESMTP id MAA14614 for <imap@u.washington.edu>; Mon, 25 Aug 1997 12:51:31 -0700
Received: from igw2.watson.ibm.com (igw2.watson.ibm.com [198.81.209.6]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.04) with ESMTP id MAA02176 for <imap@cac.washington.edu>; Mon, 25 Aug 1997 12:51:28 -0700
Received: from mailhub2.watson.ibm.com (mailhub2.watson.ibm.com [9.2.250.15]) by igw2.watson.ibm.com (8.8.7/07-11-97) with ESMTP id PAA09954 for <imap@cac.washington.edu>; Mon, 25 Aug 1997 15:48:03 -0400
Received: from uranus.diz.watson.ibm.com (uranus.diz.watson.ibm.com [9.2.35.85]) by mailhub2.watson.ibm.com (8.8.2/07-14-97) with SMTP id PAA21058 for <imap@cac.washington.edu>; Mon, 25 Aug 1997 15:51:26 -0400
Message-Id: <SIMEON.9708251520.N@uranus.diz.watson.ibm.com>
Date: Mon, 25 Aug 1997 15:51:20 -0400
Sender: IMAP-owner@u.washington.edu
Precedence: bulk
From: "Barry Leiba, Multimedia Messaging" <leiba@watson.ibm.com>
To: imap <imap@cac.washington.edu>
Subject: Re: Communciator 4.02 Imap EXPUNGE problem
In-Reply-To: <MailManager.872536294.20177.mrc@Ikkoku-Kan.Panda.COM>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET="US-ASCII"
X-Authentication: none
X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN

On Mon, 25 Aug 97 12:11:34 -0700 Mark Crispin <MRC@Panda.COM> wrote:
> It exploits a weakness in operating systems whose scheduler allocates by
> process, instead of by user.  A client which spawns multiple server 
> processes (in *ANY* protocol -- this includes HTTP) seeks to grab a greater 
> share of the server's resources (and bandwidth to the server) to the 
> detriment of clients which do not.  It adds overhead to the server because 
> these additional server processes need to be scheduled.

I agree with you if we're talking about a client that spawns multiple 
processes to try to pump more work through the server (as many HTTP 
clients do).  In this case, though, we're not talking about that - we're 
talking about the idea of a client's managing *two* (not "a bunch of") 
server processes: one to which it sends work that it thinks might be 
long-running and another to which it sends short-running work for which 
relatively prompt interactive response is desired.  The idea isn't to pump 
more work through the server, but to have one process that it knows will 
not be blocked by a long-running request.

> > Instead, let's use these experiences to clarify the spec or
> > to add to an "implementer's guide" that warns people against doing 
> > things that commonly deployed servers or mail stores or whatever can't 
> > handle well.
> 
> This isn't IMAP-specific.  It is a fundamental software engineering 
> principle, the sort of thing that belongs in CS 101.

Such management as I describe above *is* a good thing in general, and 
would, in fact, be taught in a CS class as something that one *should* do 
(as I say, for specific reasons, and not with the aim of stuffing more of 
*my* work at the server, hoping to crowd out *your* work).  If it's a 
particularly bad idea in IMAP, owing to elements of server back-ends which 
may not be obvious to many implementers, then it's worth making note of it.

Barry Leiba, Multimedia Messaging  (leiba@watson.ibm.com)
http://www.research.ibm.com/people/l/leiba