From: David Woolley <firstname.lastname@example.org> Message-Id: <199803081026.KAA11114@djwhome.demon.co.uk> To: email@example.com (Phil Peterson) Date: Sun, 8 Mar 1998 10:26:34 +0000 (GMT) Cc: firstname.lastname@example.org, uri@Bunyip.Com, email@example.com In-Reply-To: <35019BEB.A9694780@netscape.com> from "Phil Peterson" at Mar 7, 98 11:11:39 am Subject: Re: LYNX-DEV problem with 'news' url draft > > > but Netscape destroyed the distinction > > between nntp and new and I think that has now been officially sanctioned. > > I don't understand what distinction we destroyed. Would you care to say > more about that? news: refers to the global (message-id) namespace of USENET, whereas nntp refers to the local NNTP (article number) namespace of a named server. Navigator, but not MSIE started using news: for both, with the result that, with the proliferation of isolated NNTP systems, a lot of people providing product support through the NNTP protocol started to use news: instead of nntp: and effectively locked out clients other than Netscape. Effectively news: assumes real push technology, where the articles are pushed out to every *USENET* server in the world, whereas nntp: assumed that you pulled from the home server. My understanding is that the nntp: functionality has now been merged with news: to bring the standards into line with the de facto position. In some ways this is like LDAP v3 v X.500, in that again one unified distributed system is being replaced by lots of islands, for which you need to know the server before you can connect.