Re: Communciator 4.02 Imap EXPUNGE problem
"Barry Leiba, Multimedia Messaging" <leiba@watson.ibm.com> Mon, 25 August 1997 12:06 UTC
Received: from cnri by ietf.org id aa05151; 25 Aug 97 8:06 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 IAA02225 for <ietf-archive@CNRI.Reston.VA.US>; Mon, 25 Aug 1997 08:09:23 -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 FAA05742; Mon, 25 Aug 1997 05:04:35 -0700
Received: from mx2.u.washington.edu (mx2.u.washington.edu [140.142.32.7]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id FAA32464 for <imap@lists.u.washington.edu>; Mon, 25 Aug 1997 05:03:19 -0700
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mx2.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.04) with ESMTP id FAA18948 for <imap@u.washington.edu>; Mon, 25 Aug 1997 05:03:18 -0700
Received: from igw3.watson.ibm.com (igw3.watson.ibm.com [198.81.209.18]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.04) with ESMTP id FAA22622 for <imap@cac.washington.edu>; Mon, 25 Aug 1997 05:03:15 -0700
Received: from mailhub2.watson.ibm.com (mailhub2.watson.ibm.com [9.2.250.15]) by igw3.watson.ibm.com (8.8.7/07-11-97) with ESMTP id HAA09306 for <imap@cac.washington.edu>; Mon, 25 Aug 1997 07:56:39 -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 IAA17236 for <imap@cac.washington.edu>; Mon, 25 Aug 1997 08:03:13 -0400
Message-Id: <SIMEON.9708250808.A@uranus.diz.watson.ibm.com>
Date: Mon, 25 Aug 1997 08:03:08 -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.872441535.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 Sun, 24 Aug 97 09:52:15 -0700 Mark Crispin <MRC@cac.washington.edu> wrote: > I am very hard-pressed to think of any circumstance with any server in which > the client receives any benefit by opening multiple sessions to the > same mailbox on the same server -- not even when the mailbox format permits Well, I can think of one or two - note that I'm not condoning it here, just offering reasons why a client-writer might think to do it. Because there's no way for the client to know whether the server will or will not support multiple commands running simultaneously, and because some commands (such as EXPUNGE, or especially COPY and SEARCH) may take a significant amount of time to run, the client-writer, who would like to simply send the one command and allow a subsequent FETCH to run at the same time, is probably trying to guarantee that effect by doing the possibly-long-running command in another session. This clearly is a loser on an EXPUNGE of only a few messages, or a quick SEARCH or COPY (where the overhead of establishing another session outweighs the benefit), but with an EXPUNGE of hundreds of messages, for instance, or a long-running SEARCH, it can, indeed, improve the performance for the interactive session by not making it wait for the EXPUNGE or SEARCH to finish. Of course, it's done with the understanding that it can't tell whether an in-progress SEARCH will or will not allow a FETCH to run, and it doesn't take into account that it also can't tell whether the second session will interfere with the first in any significant way. 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. 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. Barry Leiba, Multimedia Messaging (leiba@watson.ibm.com) http://www.research.ibm.com/people/l/leiba
- (fwd) [Fwd: Communciator 4.02 Imap EXPUNGE proble… ccyflai
- re: (fwd) [Fwd: Communciator 4.02 Imap EXPUNGE pr… Mark Crispin
- Re: Communciator 4.02 Imap EXPUNGE problem Barry Leiba, Multimedia Messaging
- Re: Communciator 4.02 Imap EXPUNGE problem Mark Crispin
- Re: Communciator 4.02 Imap EXPUNGE problem Barry Leiba, Multimedia Messaging
- Re: Communciator 4.02 Imap EXPUNGE problem Eric Rizzo
- Re: Communciator 4.02 Imap EXPUNGE problem Mark Crispin
- Re: Communciator 4.02 Imap EXPUNGE problem Mark Crispin
- Re: Communciator 4.02 Imap EXPUNGE problem Barry Leiba, Multimedia Messaging
- Re: Communciator 4.02 Imap EXPUNGE problem Mark Crispin
- Re: Communciator 4.02 Imap EXPUNGE problem Barry Leiba, Multimedia Messaging
- Re: Communciator 4.02 Imap EXPUNGE problem Mike Macgirvin
- Re: Communciator 4.02 Imap EXPUNGE problem Mark Crispin
- Re: Communciator 4.02 Imap EXPUNGE problem Barry Leiba, Multimedia Messaging
- Re: Communciator 4.02 Imap EXPUNGE problem Mark Crispin
- Re: Communciator 4.02 Imap EXPUNGE problem Chris Hanson
- re: (fwd) [Fwd: Communciator 4.02 Imap EXPUNGE pr… Cyrus Daboo
- Re: Communciator 4.02 Imap EXPUNGE problem Barry Leiba, Multimedia Messaging
- "Minimum" and "Evil" servers Eric Rizzo
- Re: Communciator 4.02 Imap EXPUNGE problem Eric Rizzo