IETF Logo Mail Archive

Re: WG last call on draft-ietf-imapext-condstore-00.txt

Cyrus Daboo <daboo@cyrusoft.com> Sat, 12 April 2003 15:36 UTC

Received: from above.proper.com (localhost [127.0.0.1]) by above.proper.com (8.12.9/8.11.6) with ESMTP id h3CFaVJM012350 for <ietf-imapext-bks@above.proper.com>; Sat, 12 Apr 2003 08:36:31 -0700 (PDT)
Received: (from majordomo@localhost) by above.proper.com (8.12.9/8.12.9/Submit) id h3CFaVAi012349 for ietf-imapext-bks; Sat, 12 Apr 2003 08:36:31 -0700 (PDT)
X-Authentication-Warning: above.proper.com: majordomo 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.9/8.11.6) with ESMTP id h3CFaUJM012342 for <ietf-imapext@imc.org>; Sat, 12 Apr 2003 08:36:30 -0700 (PDT)
Received: from [10.0.1.3] (localhost [127.0.0.1]) by darius.cyrusoft.com (8.9.3/8.9.3) with ESMTP id LAA23981; Sat, 12 Apr 2003 11:33:02 -0400 (EDT)
Date: Sat, 12 Apr 2003 11:36:28 -0400
From: Cyrus Daboo <daboo@cyrusoft.com>
To: Alexey Melnikov <mel@messagingdirect.com>
cc: ietf-imapext@imc.org
Subject: Re: WG last call on draft-ietf-imapext-condstore-00.txt
Message-ID: <2147483647.1050147388@[10.0.1.3]>
In-Reply-To: <3E9793F0.A48EF7E2@messagingdirect.com>
References: <p06000b07babcac6d3470@[216.43.25.67]> <2147483647.1050084387@[10.0.1.6]> <3E9793F0.A48EF7E2@messagingdirect.com>
X-Mailer: Mulberry/3.1.0b1 (Mac OS X)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
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,

--On Friday, April 11, 2003 10:20 PM -0600 Alexey Melnikov 
<mel@messagingdirect.com> wrote:

|> Interaction with SORT and THREAD - note that both SORT and THREAD take
|> search criteria as arguments. Right now the draft only discusses SORT but
|> it needs to include THREAD as well (an example for a thread response with
|> MODSEQ would be good too).
|
| Why would one want to use MODSEQ with THREAD?

For the same reason one would use it in the search criteria on sort: to 
have the command return results only for those messages that changed since 
the MODSEQ. I doubt this is really a useful behaviour but it has to be 
present for consistency if you are adding MODSEQ to search unless its 
explicitly stated MODSEQ can't be used in sort/thread search criteria.

-- 
Cyrus Daboo

v2.23.0 | Report a Bug | By Email