Xref: utzoo news.software.nn:1330 news.software.b:6242 news.software.nntp:943
Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!att!emory!wuarchive!bcm!tmc.edu!sob
From: sob@tmc.edu (Stan Barber)
Newsgroups: news.software.nn,news.software.b,news.software.nntp
Subject: Re: REPLY: Why use NN when there is TRN???
Message-ID: <2867@gazette.bcm.tmc.edu>
Date: 26 Nov 90 08:01:01 GMT
References: <1990Nov23.160854.13868@vlsi.polymtl.ca> <14@grumbly.UUCP>
Sender: usenet@bcm.tmc.edu
Followup-To: news.software.nn
Organization: Baylor College of Medicine, Houston, Tx
Lines: 32
Nntp-Posting-Host: tmc.edu

In article <14@grumbly.UUCP> duc@grumbly.UUCP (Richard Ducoty) writes:
>The reason rn is the 'most popular' is that it's packed along with the
>news much of the time.  People, being the cheap, lazy creatures, 
>don't always expend the extra effort to get a decent reader.

vnews and readnews are part of BNEWS. CNEWS has its varients.
rn 4.3 came with BSD 4.3, and a patch kit to make it work with nntp was
packaged with nntp for awhile. However, rn was not and is not part of
the news distibution, per se.

Go read the document on the news software. It is posted monthly to
news.announce.newusers.

The biggest problem with nn and trn is the fact that they (currently) have
incompatible thread databases. In fact, it would be a pretty neat idea
to build some kind of standard interface for doing this kind of thing
so that it could be ported to more news readers or architecture other
than Unix! We might be able to move some of this proposed standard 
interface back into NNTP. However, Unix NNTP has enough problems trying to
cope with the differences in the two BACK-end (CNEWS and BNEWS) to be
mutilated into supporting two different threading architectures. 







-- 
Stan           internet: sob@bcm.tmc.edu         Director, Networking 
Olan           uucp: {rutgers,mailrus}!bcm!sob   and Systems Support
Barber         Opinions expressed are only mine. Baylor College of Medicine