Gnus development mailing list
 help / color / mirror / Atom feed
From: Simon Josefsson <jas@extundo.com>
Cc: ding@gnus.org
Subject: Re: automatic Agentizing of servers (was: Summary buffer
Date: Tue, 30 Dec 2003 12:16:15 +0100	[thread overview]
Message-ID: <ilu4qvir1xc.fsf@latte.josefsson.org> (raw)
In-Reply-To: <m3ad5b59oa.fsf@newsguy.com> (Harry Putnam's message of "Mon, 29 Dec 2003 20:19:49 -0600")

Harry Putnam <reader@newsguy.com> writes:

> Simon Josefsson <jas@extundo.com> writes:
>
>> But it doesn't rule out the possibility that I'm wrong. :-)
>>
>> The auto-agentification is rather simplistic, basically I believe it
>> now just work like:
>>
>> IF NOT EXISTS ~/News/agent/lib/servers THEN
>>   DOLIST (cons gnus-select-method gnus-secondary-select-methods)
>>     method = (gnus-method-to-server LISTEL)
>>     IF CAR(method) MEMBER OF gnus-agent-auto-agentize-methods
>>        ADD method TO gnus-agent-covered-methods
>>   WRITE gnus-agent-covered-methods INTO ~/News/agent/lib/servers
>
> Maybe its been explained before but I'm having trouble understanding
> why we need any auto agentization.  Seems like it should always
> require a `J a' on the server.  What is really saved or made better
> by having it automatic?

The auto-agentification make the use-agent-as-cache the default
behaviour, for remote backends.  Most MUAs these days cache the
equivalent of NOV information in groups, and I think it is useful.  If
nntp/nnimap groups were not auto-agentified, or if the user removed
those servers from the agent, entering groups with thousands of
articles would download the NOV data every time you enter the group,
this can be slow.  With the agent NOV cache, entering even groups with
20000 articles is rather fast, because almost nothing have to be
transfered over the network.

So essentially the reason for auto-agentifying some servers is that it
improves performance, and doesn't (shouldn't) affect anything else.

Steinar Bang <sb@dod.no> writes:

> Ie. I can live with today's behaviour as long as I don't have to
> remove agentizing every time I start Gnus, but I don't get why it has
> to be this way.

Hm, maybe if we look at it from the reverse point of view: why don't
you want the nntp/nnimap backends in the agent?  Does it cause any
problems?  Don't you find entering large nnimap/nntp groups slow?
I.e., waiting for all NOV data to be downloaded?  If the servers are
agentified, only the first time you enter a group will be slow.

(Btw, nnimap has its own NOV cache, but it is disabled when the agent
is enabled.  Perhaps it should only be disabled if the current server
is not in the agent, instead.  But even so, having two NOV caches
within Gnus just make it more difficult to maintain; it is easier to
fix bugs in one NOV cache than to fix them in two.  So it would be
better if the agent NOV cache was used all the time, which is what
auto-agentification achieves.  You can enable the nnimap-specific NOV
cache by toggling `nnimap-nov-is-evil'.)




  parent reply	other threads:[~2003-12-30 11:16 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-24 15:14 Summary buffer highlighting Emerick Rogul
2003-11-24 16:17 ` automatic Agentizing of servers (was: Summary buffer highlighting) Ted Zlatanov
2003-11-24 16:42   ` automatic Agentizing of servers (was: Summary buffer Emerick Rogul
2003-11-24 16:47   ` Kevin Greiner
2003-11-24 17:05     ` Emerick Rogul
2003-11-24 17:07     ` Ted Zlatanov
2003-11-25  2:48       ` Kevin Greiner
2003-11-25  8:25         ` Simon Josefsson
2003-11-25 18:31           ` Ted Zlatanov
2003-12-29 21:22           ` Steinar Bang
2003-12-29 21:39             ` Simon Josefsson
2003-12-29 21:58               ` Steinar Bang
2003-12-29 22:23                 ` Steinar Bang
2003-12-29 22:27                   ` Steinar Bang
2003-12-29 22:36                     ` Steinar Bang
2003-12-29 22:33                 ` Simon Josefsson
2003-12-29 22:44                   ` Steinar Bang
2003-12-29 23:00                     ` Simon Josefsson
2003-12-29 23:10                       ` Kevin Greiner
2003-12-29 23:17                         ` Simon Josefsson
2003-12-29 23:37                           ` Kevin Greiner
2003-12-29 23:53                             ` Simon Josefsson
2003-12-30  2:19                               ` Harry Putnam
2003-12-30  9:44                                 ` Steinar Bang
2003-12-30 11:16                                 ` Simon Josefsson [this message]
2003-12-30 20:55                                   ` Steinar Bang
2003-12-30 21:30                                     ` Simon Josefsson
2003-12-30 22:49                                       ` Harry Putnam
2003-12-31 12:55                                       ` Steinar Bang
2003-12-30  9:40                       ` Steinar Bang

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=ilu4qvir1xc.fsf@latte.josefsson.org \
    --to=jas@extundo.com \
    --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).