Sm@bhpese.bhpese.oz.au (Scott Merrilees) (02/07/90)
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 (possibly it should be configurable what information was stored in the database, thus allowing people with less ambitious news readers to use less space for the database), otherwise I can see my news spool partition being 80% news reader databases and 20% news articles. Comments? Sm -- Scott Merrilees, BHP Rod & Bar Products Division, Newcastle, Australia INTERNET: Sm@bhpese.oz.au UUCP: ...!uunet!bhpese.oz!Sm
davison@drivax.UUCP (Wayne Davison) (02/09/90)
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