From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/47374 Path: main.gmane.org!not-for-mail From: Wes Hardaker Newsgroups: gmane.emacs.gnus.general Subject: Re: Agent downloads too many headers Date: Wed, 23 Oct 2002 06:55:44 -0700 Organization: Network Associates Laboratories Sender: owner-ding@hpc.uh.edu Message-ID: References: <84u1jfvvsx.fsf@crybaby.cs.uni-dortmund.de> <84vg3td5bf.fsf@crybaby.cs.uni-dortmund.de> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable X-Trace: main.gmane.org 1035381566 6930 80.91.224.249 (23 Oct 2002 13:59:26 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Wed, 23 Oct 2002 13:59:26 +0000 (UTC) Cc: ding@gnus.org Return-path: Original-Received: from malifon.math.uh.edu ([129.7.128.13]) by main.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 184M2d-0001nM-00 for ; Wed, 23 Oct 2002 15:59:24 +0200 Original-Received: from sina.hpc.uh.edu ([129.7.128.10] ident=lists) by malifon.math.uh.edu with esmtp (Exim 3.20 #1) id 184Lzh-0007rE-00; Wed, 23 Oct 2002 08:56:21 -0500 Original-Received: by sina.hpc.uh.edu (TLB v0.09a (1.20 tibbs 1996/10/09 22:03:07)); Wed, 23 Oct 2002 08:57:06 -0500 (CDT) Original-Received: from sclp3.sclp.com (qmailr@sclp3.sclp.com [209.196.61.66]) by sina.hpc.uh.edu (8.9.3/8.9.3) with SMTP id IAA24120 for ; Wed, 23 Oct 2002 08:56:51 -0500 (CDT) Original-Received: (qmail 19857 invoked by alias); 23 Oct 2002 13:55:58 -0000 Original-Received: (qmail 19852 invoked from network); 23 Oct 2002 13:55:58 -0000 Original-Received: from adsl-66-127-127-227.dsl.scrm01.pacbell.net (HELO localhost.localdomain) (@66.127.127.227) by gnus.org with SMTP; 23 Oct 2002 13:55:58 -0000 Original-Received: (from hardaker@localhost) by localhost.localdomain (8.11.6/8.11.6) id g9NDtiO02629; Wed, 23 Oct 2002 06:55:44 -0700 Original-To: kai.grossjohann@uni-duisburg.de (Kai =?iso-8859-1?q?Gro=DFjohann?=) X-Face: #qW^}a%m*T^{A:Cp}$R\"38+d}41-Z}uU8,r%F#c#s:~Nzp0G9](s?,K49KJ]s"*7gvRgA SrAvQc4@/}L7Qc=w{)]ACO\R{LF@S{pXfojjjGg6c;q6{~C}CxC^^&~(F]`1W)%9j/iS/ IM",B1M.?{w8ckLTYD'`|kTr\i\cgY)P4 In-Reply-To: <84vg3td5bf.fsf@crybaby.cs.uni-dortmund.de> (kai.grossjohann@uni-duisburg.de's message of "Wed, 23 Oct 2002 08:42:28 +0200") User-Agent: Gnus/5.090008 (Oort Gnus v0.08) XEmacs/21.5 (brussels sprouts, i686-pc-linux) Precedence: list X-Majordomo: 1.94.jlt7 Xref: main.gmane.org gmane.emacs.gnus.general:47374 X-Report-Spam: http://spam.gmane.org/gmane.emacs.gnus.general:47374 >>>>> On Wed, 23 Oct 2002 08:42:28 +0200, kai.grossjohann@uni-duisburg.de (= Kai Gro=DFjohann) said: Kai> But the problem is this: suppose the user uses the agent for a while Kai> in the default setting, then changes gnus-agent-consider-all-articles Kai> to true later on. This means that lots of articles need to be Kai> fetched where the headers are fetched already. So at some point Kai> headers from the cache need to be added to the list of articles to Kai> check. How do I do that? Kai> Another thing is that we probably don't want to iterate over all Kai> those long-fetched headers again to see if we need to fetch the Kai> corresponding article now. So maybe along with the range of Kai> articles fetched we should store the value of Kai> gnus-agent-consider-all-articles and the predicate that was used. Kai> Then when either one changes we can consider all those Kai> long-fetched headers again and when they stay the same we only Kai> need to check the new headers. First off Kai, I thank you tremendous amounts for looking into implementing all the features I've been craving for quite some time with respect to the agent. I've never had time or brain capacity to look into it myself (and every time I think I know elisp, all I have to do is open the gnus code to prove to myself that I don't. (What the heck do ',(' and '`(' and '`[,(' mean anyway???) Anyway, the other option to the above problems is to merely document it in the variable documentation. IE, "if you change this value from nil to t, you must also run gnus-forget-all-my-agent-knowledge or something to remove the ranges you're worried about. It might be easier than implementing the idea in the second paragraph above (though that would certainly be easier for the end-user). I keep meaning to post the nnsf (sourceforge tracker/bugs/patches/... data viewing) backend I've written (it works. almost), but I need to look into agent interactions with it still and every I think about it my head starts spinning. --=20 "The trouble with having an open mind, of course, is that people will insist on coming along and trying to put things in it." -- Terry Pratche= tt