From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: Bizarre Cache Implementation
Date: 14 Aug 2000 19:59:00 +0200 [thread overview]
Message-ID: <m3og2v67x7.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <xljwvjgo1jt.fsf@abyss.eurecom.fr>
Arnd Kohrs <kohrs@acm.org> writes:
> The advantages would be fewer unwanted features (like the one above) and
> more flexibility as to where one actually stores one's cached files
> (even shared caches could be possible if the backend was nnimap (IMO a
> very useful feature for slow web-based discussion groups)).
>
> I might oversee important issues here. Also there is probably a good
> reason why the current implementation is like it is.
gnus-cache predates nnoo, which is why it is like it is.
Storing the cache in a backend of your choice sounds OK to me, but the
current cache implementation is nice and fast, so I see no pressing
need to rewrite it...
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
prev parent reply other threads:[~2000-08-14 17:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-06-23 15:32 Arnd Kohrs
2000-06-23 19:38 ` Stainless Steel Rat
2000-08-14 17:59 ` Lars Magne Ingebrigtsen [this message]
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=m3og2v67x7.fsf@quimbies.gnus.org \
--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).