Xref: utzoo news.software.b:4121 news.software.nn:90
Path: utzoo!utstat!helios.physics.utoronto.ca!jarvis.csri.toronto.edu!mailrus!cs.utexas.edu!usc!apple!amdahl!drivax!davison
From: davison@drivax.UUCP (Wayne Davison)
Newsgroups: news.software.b,news.software.nn
Subject: Re: News readers and their databases.
Keywords: rn nn database threaded
Message-ID: <GZSD7YQ@drivax.UUCP>
Date: 9 Feb 90 03:13:50 GMT
References: <1990Feb7.081537.24473@bhpese.oz.au>
Organization: Digital Research, Monterey CA
Lines: 23

Scott Merrilees (Sm@bhpese.bhpese.oz.au) wrote:
} We run both rn & nn here. Nn maintains an article database, suggested mods
} to rn to allow it to do thread following also require a database.  It would
} be nice if all news readers that use an article/subject/whatever database
} used the same database [...]

A nice idea.  I'm also curious what exactly TMNN (a.k.a. B news 3.0) does
to accomplish their threaded newsreader support.  Some sort of data format
"standard" would seem to be a good thing to get started.  I know that our
site is currently running both "mthreads" and "nnmaster", and devoting
about 10% of our newsspool size to newsreader data.

As the author of the threaded version of rn, I'm open to suggestions.  Nn's
database doesn't (as yet) have any parent/child information, nor the message
ids needed to process future articles.  If Kim goes ahead with his plans to
add thread menus to nn, such information will be added, but I don't think
he's had the time to delve into this area yet.

If anyone has previous experience, design ideas, or TMNN information, drop
me a line.
-- 
Wayne Davison          \  /| / /| \/ /| /(_)         davison@drivax.UUCP
                      (_)/ |/ /\| / / |/  \          ...!amdahl!drivax!davison