> > This has been discussed on the URI list. (If it were WIT it would
> > be easy to refer to.!) I am against the idea as it is a perversion
> > of the NNTP protocol for uses which eth HTTP protocol was designed.
> > You can do the same thing just by running a local HTTP gateway
> > into a local newsgroup.
>
> I haven't followed the URI discussion, and "perversion" is a loaded
> term. What are the reasons against remote NNTP clients?
> And how does an HHTP proxy overcome these reasons?
Sorry, "perversion" is loaded. I feel that the point of the NNTP
protocol is that it is a global flooding protocol. It has certain
properties. If an NNTP server says to you "IHAVE xxxx" you can check
to see whether you have xxxx from any other site, you can pass it on,
you can refer to it just as xxxx. Either people have that message
or they don't. Looking at the Message-ID is all you need.
By contast, in a system with private news servers, you would have to
use the full URI of style nntp://host/message-id as a reference
instead. NNTP doesn't use those URLs. Not in the "References:", not
in the protocol.
On the other hand, you are just using NNTP to give HTTP
functionality, so why not use HTTP? That does use URIs,
and has the model of retieval directly or indirectly from a
home server.
You can run cern-httpd with lines like
map /* news:/*
in the config file to allow your local news groups
news:myorg.canteen.flame
to be visible as
http:/newsgate.myorg.com/myorg.canteen.flame
True, you have to write a script if you want to allow posting.
(And you need a client with posting)
Tim