From: ShengHuo ZHU <zsh@cs.rochester.edu>
Subject: Re: Just casching NOV lines...
Date: 14 Feb 2001 16:27:24 -0500 [thread overview]
Message-ID: <5b8zn9ymyr.fsf@avocet.cs.rochester.edu> (raw)
In-Reply-To: <vafk86t0ymf.fsf@lucy.cs.uni-dortmund.de> (Kai.Grossjohann@CS.Uni-Dortmund.DE's message of "14 Feb 2001 21:59:36 +0100")
Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:
> On 14 Feb 2001, Per Abrahamsen wrote:
>
> > So I wondered, would it be possible to cache just the NOV
> > information, so when I enter a group it will just fetch the new NOV
> > headers, not all the headers it has fetched before? It would save a
> > lot of bandwidth and probably unload the server as well.
>
> Well, nnimap does this, so it must be possible. However, I don't know
> if it is possible to do this in a general fashion. Of course, it
> would be nice to have a nnovcache.el which can be used by any
> backend. Hm.
I am thinking of using nnagent.el. The thought is to make
gnus-agent-covered-methods more flexible (or introduce a new variable)
so that gnus-agent can be customized to cover only retrieving headers
for some servers. Moreover, users could be benefited from gnus-agent
without switching between plugged and unplugged, i.e. a more
transparent agent implementation. However, it is just a thought. I
can't implement it in a short time.
Any comment?
ShengHuo
--
(setq gnus-posting-styles
'((".*" (signature (format "(setq gnus-posting-styles
'%S)" gnus-posting-styles)))))
next prev parent reply other threads:[~2001-02-14 21:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-14 15:08 Per Abrahamsen
2001-02-14 20:59 ` Kai Großjohann
2001-02-14 21:27 ` ShengHuo ZHU [this message]
2001-02-15 9:46 ` Simon Josefsson
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=5b8zn9ymyr.fsf@avocet.cs.rochester.edu \
--to=zsh@cs.rochester.edu \
/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).