From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: Header caching
Date: 30 Mar 1997 10:53:26 +0200 [thread overview]
Message-ID: <m2afnlzrp5.fsf@proletcult.slip.ifi.uio.no> (raw)
In-Reply-To: Joe Hildebrand's message of 26 Mar 1997 12:55:32 -0600
Joe Hildebrand <hildjj@mindspring.com> writes:
> Does Gnus provide a method for caching headers?
Not beyond the normal cache header thing, which means that the
articles are cached as well.
I'm not sure whether it's worthwhile caching just headers. Although
we will be getting that for free when I start implementing nnagent, I
guess.
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
next prev parent reply other threads:[~1997-03-30 8:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-03-26 18:55 Joe Hildebrand
1997-03-30 8:53 ` Lars Magne Ingebrigtsen [this message]
1997-03-30 22:01 ` David Moore
1997-03-31 10:38 ` Lars Magne Ingebrigtsen
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=m2afnlzrp5.fsf@proletcult.slip.ifi.uio.no \
--to=larsi@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).