re: (fwd) [Fwd: Communciator 4.02 Imap EXPUNGE problem]

Cyrus Daboo <daboo@cyrusoft.com> Wed, 27 August 1997 15:25 UTC

Received: from cnri by ietf.org id aa07982; 27 Aug 97 11:25 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 LAA10323 for <ietf-archive@CNRI.Reston.VA.US>; Wed, 27 Aug 1997 11:28:44 -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 IAA24372; Wed, 27 Aug 1997 08:19:17 -0700
Received: from mx5.u.washington.edu (mx5.u.washington.edu [140.142.32.6]) by lists.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id IAA41956 for <imap@lists.u.washington.edu>; Wed, 27 Aug 1997 08:18:09 -0700
Received: from mx1.cac.washington.edu (mx1.cac.washington.edu [140.142.32.1]) by mx5.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.04) with ESMTP id IAA25008 for <imap@u.washington.edu>; Wed, 27 Aug 1997 08:18:08 -0700
Received: from darius.cyrusoft.com (darius.cyrusoft.com [206.31.218.194]) by mx1.cac.washington.edu (8.8.4+UW97.07/8.8.4+UW97.04) with ESMTP id IAA14507; Wed, 27 Aug 1997 08:17:54 -0700
Received: from sardis.cyrusoft.com (sardis.cyrusoft.com [206.31.218.203]) by darius.cyrusoft.com (8.8.5/8.8.5) with SMTP id LAA11896; Wed, 27 Aug 1997 11:17:21 -0400 (EDT)
Message-Id: <441915.3081669630@sardis.cyrusoft.com>
Date: Wed, 27 Aug 1997 11:20:30 -0400
Sender: IMAP-owner@u.washington.edu
Precedence: bulk
From: Cyrus Daboo <daboo@cyrusoft.com>
To: imap@cac.washington.edu
Cc: Mark Crispin <MRC@cac.washington.edu>
Subject: re: (fwd) [Fwd: Communciator 4.02 Imap EXPUNGE problem]
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Authenticated: daboo by imap.cyrusoft.com
X-Licensed-To: Cyrus Daboo
X-Listprocessor-Version: 8.1 beta -- ListProcessor(tm) by CREN

Hi,
Can we go back to the original point in this discussion:

--On Sun, Aug 24, 1997 9:52 AM -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
such
> multiple access.  I can think of many circumstances in which such
behavior is
> extremely detrimental to the server, and in which such behavior can be
> detrimental to the human user.

My question is how are you supposed to deal with shared mailboxes if you
don't allow simultaneous access to a single mailbox? From my perspective I
see shared mailboxes as one of the more important benefits of IMAP over
POP, and I'm certainly promoting this to potential IMAP users now that
we've added ACL suuport into our client.

In the shared mailbox environment I would expect a single client to only
open one Read-Write (SELECT) connection to a mailbox, but multiple clients
can have multiple SELECTs to the same mailbox. For my own implementation
of searching I was planning on allowing the client to open an additional
Read-Only (EXAMINE) connection to an already SELECT'ed mailbox to do
searching if it is clear that searching the mailbox may be time consuming
and that the LOGIN/EXAMINE sequence has low overhead. This would probably
be set as a user configurable option. I may be persuaded by the arguments
against a single client opening more than one connection and change things
accordingly, but this does not address the shared mailbox issue.


~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Cyrus Daboo                                   mailto:daboo@cyrusoft.com
Cyrusoft International, Inc.                    http://www.cyrusoft.com
Voice: +1 412 605 0499                             Fax: +1 412 605 0705
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
     Proud Purveyors of Mulberry: Internet Mail from the Ground Up
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~