Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!rutgers!usc!ucsd!brian From: brian@ucsd.EDU (Brian Kantor) Newsgroups: news.software.b Subject: Re: C news compatibility with NNTP Keywords: pollyana Message-ID: <1909@ucsd.EDU> Date: 19 Aug 89 15:19:51 GMT References: <1989Aug9.164003.20669@utzoo.uucp> <6717@dayton.UUCP> <1989Aug17.171000.23302@utzoo.uucp> <64033@uunet.UU.NET> <1989Aug18.102335.17269@utstat.uucp> <6722@cs.utexas.edu> Reply-To: brian@ucsd.edu (Brian Kantor) Organization: The Avant-Garde of the Now, Ltd. Lines: 21 In article <6722@cs.utexas.edu> fletcher@cs.utexas.edu (Fletcher Mattox) writes: >If C news is backward compatible with B news, then why do I have to >have to modify NNTP to work with with C news? > >Fletcher Now wait a minute: You don't have to modify NNTP to work with C news. You might have to modify the particular implementation that you have, but you don't have to modify the PROTOCOL, dammit. NNTP was designed to be as independent of the underlying news storage and retrieval systems as we could economically make it. I think we mostly succeeded. Certainly I don't know of any major incompatabilities between the PROTOCOL and the use of C news for storage and retrieval. Remember that you're probably using an implementation of NNTP that was probably designed for interoperation with B news. That you'd have to modify it for the changed internals of a new news system, especially one that only claims compatability at the RFC level, shouldn't surprise you at all. - Brian