Re: New draft: SEARCH return options

Cyrus Daboo <daboo@isamet.com> Mon, 14 February 2005 21:40 UTC

Received: from above.proper.com (localhost.vpnc.org [127.0.0.1]) by above.proper.com (8.12.11/8.12.9) with ESMTP id j1ELetCa056483; Mon, 14 Feb 2005 13:40:55 -0800 (PST) (envelope-from owner-ietf-imapext@mail.imc.org)
Received: (from majordom@localhost) by above.proper.com (8.12.11/8.12.9/Submit) id j1ELeq6u056462; Mon, 14 Feb 2005 13:40:53 -0800 (PST)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-imapext@mail.imc.org using -f
Received: from darius.cyrusoft.com (darius.cyrusoft.com [63.163.82.2]) by above.proper.com (8.12.11/8.12.9) with ESMTP id j1ELenT0056391 for <ietf-imapext@imc.org>; Mon, 14 Feb 2005 13:40:49 -0800 (PST) (envelope-from daboo@isamet.com)
Received: from ninevah.cyrusoft.com (ninevah.cyrusoft.com [63.163.82.9]) (authenticated bits=0) by darius.cyrusoft.com (8.12.9/8.12.9) with ESMTP id j1EK0V6g024312 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 14 Feb 2005 15:00:31 -0500
Date: Mon, 14 Feb 2005 15:09:28 -0500
From: Cyrus Daboo <daboo@isamet.com>
To: Alexey Melnikov <Alexey.Melnikov@isode.com>, IMAP Extensions WG <ietf-imapext@imc.org>
cc: Lemonade WG <lemonade@ietf.org>
Subject: Re: New draft: SEARCH return options
Message-ID: <81E5C72B6B352251B49C0B64@ninevah.cyrusoft.com>
In-Reply-To: <4210BC19.4070207@isode.com>
References: <200502112027.PAA05610@ietf.org> <4210BC19.4070207@isode.com>
X-Mailer: Mulberry/4.0.0a5 (Mac OS X)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Spam-Status: No, hits=0.1 tests=LINES_OF_YELLING,LINES_OF_YELLING_2
Sender: owner-ietf-imapext@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-imapext/mail-archive/>
List-ID: <ietf-imapext.imc.org>
List-Unsubscribe: <mailto:ietf-imapext-request@imc.org?body=unsubscribe>

Hi Alexey,
I think you need to have some mention of how this interacts with 
draft-melnikov-imap-search-res-01.txt. Or that document should mention how 
it interacts with draft-melnikov-imap-search-ret-00.txt. One issue is:

a SEARCH RETURN (COUNT) UNSEEN

Strictly speaking the above command does not generate a message sequence 
set, so is the last search result $ item set or not?

There is also an interesting possibility of tying the two together via the 
ID return option I proposed. For example:

C: a SEARCH RETURN (ID 1 ALL) UNSEEN
C: a SEARCH RETURN (ID 2 ALL) DELETED
...

C: FETCH $[1] (UID INTERNALDATE FLAGS RFC822.HEADER)

C: FETCH $[2] (UID INTERNALDATE FLAGS RFC822.HEADER)

The fetch commands act on the result of the different searches, referenced 
by the ID option value. This means that a client could use multiple search 
result sets simultaneously, as opposed to in series, as they would have to 
right now.

This could prove very powerful for clients that want to present multiple 
simultaneous 'views' on the same mailbox.

-- 
Cyrus Daboo