Re: Communciator 4.02 Imap EXPUNGE problem

Eric Rizzo <erizzo@deathstar.med.miami.edu> Mon, 25 August 1997 20:19 UTC

Received: from cnri by ietf.org id aa20004; 25 Aug 97 16:19 EDT
Received: from lists2.u.washington.edu (root@lists2.u.washington.edu [140.142.56.1]) by cnri.reston.va.us (8.8.5/8.7.3) with ESMTPid QAA04305 for <ietf-archive@CNRI.Reston.VA.US>; Mon, 25 Aug 1997 16:22:42 -0400 (EDT)
Received: from host (lists.u.washington.edu [140.142.56.13]) by lists2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with SMTP id NAA06555; Mon, 25 Aug 1997 13:19:15 -0700
Received: from mx4.u.washington.edu (mx4.u.washington.edu [140.142.33.5]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id NAA24160 for <imap@lists.u.washington.edu>; Mon, 25 Aug 1997 13:18:25 -0700
Received: from obsidian.eng.miami.edu (obsidian.eng.miami.edu [129.171.33.127]) by mx4.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.04) with SMTP id NAA16082 for <imap@u.washington.edu>; Mon, 25 Aug 1997 13:18:21 -0700
Received: by obsidian.eng.miami.edu (5.65/DEC-Ultrix/4.3) id AA25280; Mon, 25 Aug 1997 16:17:42 -0400
Received: from india (india.eng.miami.edu) by hercules.ece.miami.edu (4.1/SMI-4.1) id AA17001; Mon, 25 Aug 97 16:21:09 EDT
Message-Id: <3401E89E.31FA@deathstar.med.miami.edu>
Date: Mon, 25 Aug 1997 16:18:38 -0400
Sender: IMAP-owner@u.washington.edu
Precedence: bulk
From: Eric Rizzo <erizzo@deathstar.med.miami.edu>
To: IMAP <imap@u.washington.edu>
Subject: Re: Communciator 4.02 Imap EXPUNGE problem
References: <MailManager.872536294.20177.mrc@Ikkoku-Kan.Panda.COM>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Sender: erizzo@deathstar.med.miami.edu
X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN

> 
> On Mon, 25 Aug 1997 08:03:08 -0400 (Eastern Daylight Time), Barry Leiba,
> Multimedia Messaging wrote:
> > Then, again, there is nothing in the RFC that indicates that one shouldn't
> > do this.  I repeat, yet one more time, that tossing criticism around for
> > someone's "doing such a bizarre thing", and accusing that client of "highly
> > anti-social" behaviour, when the client-writer followed the spec is
> > inappropriate.
> 
<snip>
> 
> > 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.
> 

As a IMAP-concerned "developer," I for one agree with these two
statements.  Those who monitor this list, and especially Mr. Crispin,
might notice that I've been asking a number of questions over the last
few months, and most of them are related to clarifications on issues I
could not 100% resolve by reading the RFC alone.  I think some sort of
"Implementor's Guide" would be an invaluable tool for people/groups
trying to make clients and servers that are as inter-operable as
possible.  Of course, I can imagine how busy the original RFC author(s)
are with projects, but I think someone, or a small group of us (IMAP
developers) should be able to come up with this kind of thing.  

Aside: A client that uses 2 seperate connections (sessions) as described
by Mr. Leiba, makes the server load/work/WhaterverYouCallIt O(2n)
instead of O(n) (n being the number of concurrent users), doesn't it? 
In the CS 3xx course I took, it was taught that O(xn) is really no worse
off than O(n), for reasonble x integer values.

I think we've all got to work together to bring IMAP to the rest of the
world...

-- 
Eric Nicholas Rizzo                            University of Miami
erizzo@deathstar.med.miami.edu    http://www.ece.miami.edu/~erizzo
------------------------------------------------------------------
"A man talking sense to himself is no more insane than a man
talking nonsense not to himself...or just as insane."
                      -Rosencrantz and Guildenstern Are Dead