From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/70415 Path: news.gmane.org!not-for-mail From: David Engster Newsgroups: gmane.emacs.gnus.general Subject: Re: request-group-articles for nnimap Date: Fri, 03 Sep 2010 20:10:41 +0200 Message-ID: <8739tqitpa.fsf@randomsample.de> References: <87aao05t55.fsf@lifelogs.com> <87bp8gflj5.fsf@keller.adm.naquadah.org> <87pqwwgyjb.fsf@mid.gehheimdienst.de> <874oe85l97.fsf@lifelogs.com> <87mxrzyosw.fsf_-_@lifelogs.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: dough.gmane.org 1283537490 24067 80.91.229.12 (3 Sep 2010 18:11:30 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Fri, 3 Sep 2010 18:11:30 +0000 (UTC) To: ding@gnus.org Original-X-From: ding-owner+M18790@lists.math.uh.edu Fri Sep 03 20:11:29 2010 Return-path: Envelope-to: ding-account@gmane.org Original-Received: from util0.math.uh.edu ([129.7.128.18]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1OrajX-0005OW-Dn for ding-account@gmane.org; Fri, 03 Sep 2010 20:11:27 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.math.uh.edu) by util0.math.uh.edu with smtp (Exim 4.63) (envelope-from ) id 1Oraj8-0008TM-74; Fri, 03 Sep 2010 13:11:02 -0500 Original-Received: from mx1.math.uh.edu ([129.7.128.32]) by util0.math.uh.edu with esmtps (TLSv1:AES256-SHA:256) (Exim 4.63) (envelope-from ) id 1Oraj6-0008T7-Eu for ding@lists.math.uh.edu; Fri, 03 Sep 2010 13:11:00 -0500 Original-Received: from quimby.gnus.org ([80.91.231.51]) by mx1.math.uh.edu with esmtp (Exim 4.72) (envelope-from ) id 1Oraj3-0001O3-GH for ding@lists.math.uh.edu; Fri, 03 Sep 2010 13:10:59 -0500 Original-Received: from m61s02.vlinux.de ([83.151.21.164]) by quimby.gnus.org with esmtp (Exim 3.36 #1 (Debian)) id 1Oraj2-0007ER-00 for ; Fri, 03 Sep 2010 20:10:56 +0200 Original-Received: from dslc-082-082-174-027.pools.arcor-ip.net ([82.82.174.27] helo=spaten) by m61s02.vlinux.de with esmtpsa (TLS1.0:DHE_RSA_AES_128_CBC_SHA1:16) (Exim 4.69) (envelope-from ) id 1Oraj1-0002kh-Qd for ding@gnus.org; Fri, 03 Sep 2010 20:10:56 +0200 In-Reply-To: <87mxrzyosw.fsf_-_@lifelogs.com> (Ted Zlatanov's message of "Fri, 03 Sep 2010 07:49:51 -0500") User-Agent: Gnus/5.110011 (No Gnus v0.11) Emacs/23.2 (gnu/linux) Mail-Copies-To: never Mail-Followup-To: ding@gnus.org X-Spam-Score: -1.9 (-) List-ID: Precedence: bulk Xref: news.gmane.org gmane.emacs.gnus.general:70415 Archived-At: Ted Zlatanov writes: > On Thu, 02 Sep 2010 16:39:11 +0200 David Engster wrote: > > DE> Yes, exactly. The nnimap-request-group-articles I posted simply returns > DE> the list of available article numbers in that group (which could be > DE> further compressed into the above range notation). Requesting the range > DE> of articles can take a second for very large groups, so some kind of > DE> caching should be done. > > Let the backend decide if caching is possible since it has the best > knowledge of when the data is old. It also knows best where to cache > (on the server, in memory, on disk, etc.) The caching policy can be set > globally, but the rest should be on the backend IMO. Yes, it's probably easier when the backend does it. But we can worry about that later. :-) > DE> Anyway, this would be an optional back end function, and Gnus can query > DE> the back end for availability and use it (if the user wants it). I for > DE> example don't have much problems with the article count, but I don't > DE> delete much and use Dovecot. But there are IMAP servers out there > DE> (Zimbra...) which use absolutely insane values for article numbers; > DE> maybe it's using those for Mersenne prime searching or something. > > So there's two pieces: the general facility and support for it in > nnimap. Let's get the nnimap piece done first and verify it works since > we're close. Can you modify your function to do compressed ranges? It's a simple matter of calling gnus-compress-sequence. > Do you know of any alternate implementations or patches (I haven't > kept track)? As I wrote, Vitaly already had patches, also for the general backend, but he extended the active information, without the usage of a new API function. I think his patches can still be seen here: http://repo.or.cz/w/more-gnus.git My last test of those patches still showed some problems (see http://thread.gmane.org/gmane.emacs.gnus.general/67238/focus=67407), but they already show which parts of Gnus are affected. We should first decide if we should build upon Vitaly's work with the extended active, or if we use 'nnchoke-request-group-articles'. I have difficulties following Lars' programming spree; maybe he has already committed something which has decided this. ;-) -David