From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: NOV code in Gnus
Date: Sat, 28 Dec 2002 19:38:07 +0100 [thread overview]
Message-ID: <m3r8bydgea.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <m2vg28vzni.fsf@tnuctip.rychter.com>
Jan Rychter <jan@rychter.com> writes:
> Ah, yes, my description wasn't very good. I was thinking about something
> the other way around. Say I'd like to provide another implementation for
> storing NOV data. There seems to be no easy way to do this, as the
> knowledge about the implementation of NOV storage is scattered around,
> and there are many functions that assume that it's just going to be text
> files.
Well, that is what NOV files are, isn't it? :-)
But, yes, the NOV parsing/generating code is somewhat confused, both
for hysterical reasons and for reasons of efficiency. For instance,
`nnheader-parse-overview-file' just, well, parses a NOV file, while
`gnus-get-newsgroup-headers-xover' parses a NOV file while doing
threading, gathering, washing and making a nice 5-course meal for the
entire family.
> So, I'm thinking about a unified interface for storing and accessing NOV
> data.
The actual number of places that NOV files are stored/accessed is
also quite large, but most of them use the nnheader functions for
generating/parsing the files.
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
prev parent reply other threads:[~2002-12-28 18:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <m2bs40xuq6.fsf@tnuctip.rychter.com>
2002-12-05 17:34 ` Kai Großjohann
2002-12-05 17:58 ` Paul Jarc
[not found] ` <m2vg28vzni.fsf@tnuctip.rychter.com>
2002-12-06 2:16 ` Paul Jarc
2002-12-06 13:41 ` Kai Großjohann
2002-12-06 16:22 ` Kai Großjohann
2002-12-28 18:38 ` 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=m3r8bydgea.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).