Re: Agent downloads too many headers

[kai.grossjohann@uni-duisburg.de (Kai Großjohann)]

kai.grossjohann@uni-duisburg.de (Kai Großjohann) writes:

> Suppose I tell the agent to fetch articles.  Then I read things
> offline and compose things and later on I send the queue.  Then I'm
> back online and don't use the agent for a while.  I read some
> messages while I'm online.  Then I tell the agent to fetch articles
> in order to go offline.  Here is the crucial point.  I want the
> articles to be fetched that I've read while I was online.
>
> The question is now how to achieve this.
>
> For each group, the agent should store a list (range) of articles
> considered already.  This list (range) should be updated whenever the
> user does `J s' or `J u' in the group buffer.  So it should be
> updated from gnus-agent-fetch-group-1.  That function calls
> gnus-agent-fetch-headers to get the articles to consider.  So that's
> where we need to store our data.
>
> I think we're getting closer.  Do you follow my logic?  Is it right?

I couldn't wait.  I tried to implement this, and now, finally, I
think it at least does _something_.

Henrik, is it fetching less now?

I've committed this so that others can hack on it while I sleep :-)
Another reason is that tomorrow morning before I got to rush off to
catch the train, the agent fetching will be quicker :-)

kai
-- 
~/.signature is: umop ap!sdn    (Frank Nobis)