Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!elroy.jpl.nasa.gov!turnkey!orchard.la.locus.com!fafnir.la.locus.com!fafnir.la.locus.com!richard From: richard@locus.com (Richard M. Mathews) Newsgroups: news.software.b Subject: Re: news.software.cnews, anyone? Message-ID: Date: 3 Jan 91 19:19:22 GMT References: <1990Dec29.142103.3886@blilly.UUCP> <1990Dec31.082711.6700@xenitec.on.ca> <3087@crdos1.crd.ge.COM> Organization: Locus Computing Corporation, Los Angeles, California Lines: 32 tim@delluk.uucp (Tim Wright) writes: >lear@turbo.bio.net (Eliot) writes: >>Perhaps what we >>should have (after figuring out how to rename groups without pissing >>off the world) is news.software.transport and news.software.readers. >That would seem to be the most sensible way of dividing it. Anybody else >think so ? Aren't there really 3 levels of software: 1. Software to handle communications protocols, such as nntp. This is what I think of as "transport". 2. Spoolers such as B News and C News which receive incoming articles, determine where to send articles (without actually sending them), store articles, expire articles, and insert new articles into the stream. 3. Human interfaces, which include stuff for reading, posting, manipulating, and monitoring news. By "manipulating, I mean stuff like newsetup, nngoback, and nntidy. By "monitoring" I mean stuff like nnstats and nnusage. There is a lot more here than "readers". (I'm cheating a little since 2 of the 5 programs I listed are links to "nn" itself.) I'm not sure what I would call these 3 groups. Perhaps n.s.transport, n.s.spoolers, and n.s.readers, but I don't think any of those names are really great. Richard M. Mathews D efend richard@locus.com E stonian-Latvian-Lithuanian lcc!richard@seas.ucla.edu I ndependence ...!{uunet|ucla-se|turnkey}!lcc!richard