Re: Benchmarking Gnus

[Steinar Bang <sb@dod.no>]

>>>>> Simon Josefsson <jas@extundo.com>:

> On Fri, 1 Feb 2002, ShengHuo ZHU wrote:

>>> If you mean: "if you run expiry when unplugged, are the results
>>> transferred to the nnimap group, when you go plugged?", the answer
>>> was no, the last time I tried.

>> Gnus should skip expiring offline servers, shouldn't it?

> IMHO it should remember the expiry command and run it when you get
> back online. 

That's what I would think.

> Hm.  But the conditions that decides which articles should be
> expired could have changed until then. 

Some articles may have been ticked from a different client, you mean?
If they have, Gnus should detect that, not delete the article, import
the flags for the changed articles into agent, fetching or re-fetching
copies of the articles if neccessary.

This may be more than a 5-liner...:-) but see below.

> Nah, I think you are right, if you want to expire a group, you need
> to be online.  If you are offline, maybe it should expire the local
> agent directory instead.  Opinions?

IMO an agentized group should reflect the underlying group as closely
as possible.  This means that all operations, including move and
expiry, should be available, and operate the same way as they do when
plugged.

The basic worldview is that the underlying group is the master, and
that the agent group will reflect the master as closely as possible.

This goes for nnimap groups.  Ie. if an article has been deleted on
the server, I would like the article to be deleted in the agent as
well, even if I had it ticked there.

However, for nntp, I have a different requirement.  On nntp, I would
like to keep a ticked article, even if the article have been expired
on the server.

Though I can live with an identical behaviour to what I see with
nnimap, if it is still possible to save local copies of articles, in
the way we did before agent.  Is it?