[lemonade] Re: [MORG] Context update
Timo Sirainen <tss@iki.fi> Thu, 17 May 2007 15:49 UTC
Return-path: <lemonade-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HoiDu-000104-Ju; Thu, 17 May 2007 11:49:02 -0400
Received: from lemonade by megatron.ietf.org with local (Exim 4.43) id 1HoiDt-0000zw-OO for lemonade-confirm+ok@megatron.ietf.org; Thu, 17 May 2007 11:49:01 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HoiDt-0000zo-Ec; Thu, 17 May 2007 11:49:01 -0400
Received: from dovecot.org ([213.157.71.38]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HoiDr-0006bn-TS; Thu, 17 May 2007 11:49:01 -0400
Received: from [192.168.10.2] (82-203-162-146.dsl.gohome.fi [82.203.162.146]) by dovecot.org (Postfix) with ESMTP id 5F374F0C89; Thu, 17 May 2007 18:48:58 +0300 (EEST)
From: Timo Sirainen <tss@iki.fi>
To: Dave Cridland <dave@cridland.net>
In-Reply-To: <30512.1179169211.052893@peirce.dave.cridland.net>
References: <30512.1179169211.052893@peirce.dave.cridland.net>
Date: Thu, 17 May 2007 18:48:58 +0300
Message-Id: <1179416938.32181.856.camel@hurina>
Mime-Version: 1.0
X-Mailer: Evolution 2.10.1
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a1852b4f554b02e7e4548cc7928acc1f
Cc: Enhancements to Internet email to support diverse service enivronments <lemonade@ietf.org>, Messaging Organization <morg@ietf.org>
Subject: [lemonade] Re: [MORG] Context update
X-BeenThere: lemonade@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Enhancements to Internet email to support diverse service enivronments <lemonade.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/lemonade>, <mailto:lemonade-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:lemonade@ietf.org>
List-Help: <mailto:lemonade-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/lemonade>, <mailto:lemonade-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1023990504=="
Errors-To: lemonade-bounces@ietf.org
On Mon, 2007-05-14 at 20:00 +0100, Dave Cridland wrote: > I've just submitted update to my IMAP CONTEXT draft. > > I've put it up at > http://dave.cridland.net/draft-cridland-imap-context-02.txt until > it's announced. I'm planning on implementing virtual mailboxes to my server, but I think CONTEXT won't be integrated with that feature. CONTEXT seems like it's useful for temporary views of mailboxes, while actual virtual mailboxes are more permanent and often generated from multiple physical mailboxes. For example CONTEXT mentions virtual Trash, but people usually want the Trash to contain \Deleted messages from all the mailboxes, not just one. Also since CONTEXT requires that the mailbox is selected and so all the flag changes, expunges etc. are sent to clients, this doesn't really give server the possibility of optimizing the search views the same way as separate virtual mailboxes would. I could still implement CONTEXT, but I think saying virtual mailboxes could be implemented with it is a bit misleading. At least I was expecting CONTEXT to be quite different. I read the draft now for the first time without knowing anything about CONTEXT before that. Some comments: 3.1: "Such servers also accept three additional return options, and provide three new result data items, and no new responses." I've no idea what return options or result data items are at this point. After reading far enough down I finally figure out it's talking about ESEARCH. So mentioning [ESEARCH] already in the first sentence would be helpful. 3.2: "The return option CONTEXT SHOULD be used by a client to indicate that subsequent use of the criteria are likely." "the search criteria" would have helped me to understand this more easily. 3.3.2: The client MUST process (and the server MUST generate) ADDTO and REMOVEFROM return data items in order, including those within a single ESEARCH response. What order? 3.3.3: The ADDTO return data item MAY include several new results to be inserted - therefore it is imporant to note that the positions included in a single ADDTO return data item contain positions before the shifting due to other new results take place. I can't parse that sentence. I'm guessing it means that if there are multiple results the shifting needs to be done after processing the next result. Or exactly the opposite. If the position is non-zero, the new results in the update are to be What if it's zero? I don't think I understand this position thing at all since it can even be ignored by clients. Or is it related to SORT? 3.3.4: S: * ESEARCH (TAG "B01") UID REMOVEFROM 32768 C: B03 NOOP S: * EXPUNGE 23762 S: B03 OK Nothing done. "* 23762 EXPUNGE". And maybe a note that the REMOVEFROM MUST be sent before the EXPUNGE (at least with sequences). 3.3.5: The server MAY free any resource associated with a context so disabled. ? 3.4: Where a PARTIAL search return option references results which do not exist, by using a range which starts or ends higher than the COUNT of results, then the server returns those results which are in the set. This yields a PARTIAL return data item which has, as payload, the original range and a potentially missing set of results which may be shorter than the extent of the range. This paragraph is somewhat weird. It's not necessary to do COUNT for a partial SEARCH, so mentioning COUNT in there isn't probably right. And if the mailbox had changed since the COUNT was returned, the range does exist. Unless that's what the last sentence tries to say with "missing set of results"? Also the section doesn't mention anything about problems if the mailbox changes. So: C: A03 UID SEARCH RETURN (PARTIAL 1:500) UNDELETED UNKEYWORD $Junk .. C: A04 UID SEARCH RETURN (PARTIAL 501:1000) UNDELETED UNKEYWORD $Junk S: * 1 FETCH (FLAGS $Junk) .. Now this most likely means that the original 501th result was actually skipped, because the first message had $Junk keyword set and the partial result set got moved by one. Right?
_______________________________________________ lemonade mailing list lemonade@ietf.org https://www1.ietf.org/mailman/listinfo/lemonade Supplemental Web Site: http://www.standardstrack.com/ietf/lemonade
- [lemonade] Context update Dave Cridland
- RE: [lemonade] Context update Zoltan.Ordogh
- [lemonade] Re: [MORG] Context update Timo Sirainen
- RE: [lemonade] Re: [MORG] Context update Zoltan.Ordogh
- RE: [lemonade] Re: [MORG] Context update Dave Cridland
- [lemonade] Re: [MORG] Context update Dave Cridland
- [lemonade] Re: [MORG] Context update Alexey Melnikov