Gnus development mailing list
 help / color / mirror / Atom feed
From: Wes Hardaker <wes@hardakers.net>
Cc: ding@gnus.org
Subject: Re: Agent downloads too many headers
Date: Wed, 23 Oct 2002 06:55:44 -0700	[thread overview]
Message-ID: <sdisztuun3.fsf@wanderer.hardakers.net> (raw)
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")

>>>>> On Wed, 23 Oct 2002 08:42:28 +0200, kai.grossjohann@uni-duisburg.de (Kai Großjohann) 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.

-- 
"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 Pratchett



  reply	other threads:[~2002-10-23 13:55 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-22  6:20 Kai Großjohann
2002-10-23  6:42 ` Kai Großjohann
2002-10-23 13:55   ` Wes Hardaker [this message]
2002-10-23 14:30     ` Kai Großjohann
2002-10-23 14:31     ` Kai Großjohann
2002-10-23 19:14     ` Josh Huber
2002-10-23 15:54 ` Kai Großjohann
2002-10-23 20:33   ` Kai Großjohann
2002-10-23 21:42     ` Henrik Enberg
2002-10-24  7:14       ` Kai Großjohann
2002-10-24 20:51         ` Henrik Enberg
2002-10-25  8:36           ` Kai Großjohann
2002-10-25  7:32     ` Danny Siu

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=sdisztuun3.fsf@wanderer.hardakers.net \
    --to=wes@hardakers.net \
    --cc=ding@gnus.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).