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

Alexey Melnikov <mel@messagingdirect.com> Sun, 20 April 2003 05:38 UTC

Received: from above.proper.com (localhost [127.0.0.1]) by above.proper.com (8.12.8p1/8.12.8) with ESMTP id h3K5cht2031851 for <ietf-imapext-bks@above.proper.com>; Sat, 19 Apr 2003 22:38:43 -0700 (PDT) (envelope-from owner-ietf-imapext@mail.imc.org)
Received: (from majordom@localhost) by above.proper.com (8.12.8p1/8.12.9/Submit) id h3K5chbb031850 for ietf-imapext-bks; Sat, 19 Apr 2003 22:38:43 -0700 (PDT)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-imapext@mail.imc.org using -f
Received: from rembrandt.esys.ca (rembrandt.esys.ca [198.161.92.131]) by above.proper.com (8.12.8p1/8.12.8) with ESMTP id h3K5cft2031845 for <ietf-imapext@imc.org>; Sat, 19 Apr 2003 22:38:41 -0700 (PDT) (envelope-from mel@messagingdirect.com)
Received: from messagingdirect.com (1Cust193.tnt3.edmonton.ab.da.uu.net [64.10.184.193]) (authenticated) by rembrandt.esys.ca (8.11.6/8.11.0.Beta0) with ESMTP id h3K5g8V29498; Sat, 19 Apr 2003 23:42:08 -0600
Message-ID: <3EA226A8.C4AC1C0A@messagingdirect.com>
Date: Sat, 19 Apr 2003 22:48:40 -0600
From: Alexey Melnikov <mel@messagingdirect.com>
Organization: ACI WorldWide / MessagingDirect
X-Mailer: Mozilla 4.79 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Mark Crispin <mrc@CAC.Washington.EDU>
CC: Cyrus Daboo <daboo@cyrusoft.com>, ietf-imapext@imc.org
Subject: Re: WG last call on draft-ietf-imapext-condstore-00.txt
References: <p06000b07babcac6d3470@[216.43.25.67]> <2147483647.1050084387@[10.0.1.6]> <3E9793F0.A48EF7E2@messagingdirect.com> <2147483647.1050147388@[10.0.1.3]> <Pine.LNX.4.55.0304121013330.14139@shiva0.cac.washington.edu>
Content-Type: text/plain; charset="koi8-r"
Content-Transfer-Encoding: 7bit
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>

Mark Crispin wrote:

> On Sat, 12 Apr 2003, Cyrus Daboo wrote:
> > | 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.
>
> I'm hard-pressed to think of a use for MODSEQ with THREAD; and while SORT
> presents some possible use I doubt that there would be much of that in
> real life.

I agree with Mark here.
I can see a utility in MODSEQ criterion in SEARCH and MODSEQ sort order in SORT.

I prefer to live it unspecified how MODSEQ search criteria can be used in
THREAD. Any objections?

> If you declare that MODSEQ is an additional argument to SEARCH (much as
> CHARSET is) instead of a SEARCH criterion, then you avoid the issue.  But
> that's no good if you decide to have MODSEQ in SORT.

Regards,
Alexey
__________________________________________
R & D, ACI Worldwide/MessagingDirect
Watford, UK

Work Phone: +44 1923 81 2877
Home Page: http://orthanc.ab.ca/mel

I speak for myself only, not for my employer.
__________________________________________