[NNTP] LIST EXTENSIONS and an NNTPv2 capability
Clive D.W. Feather
clive at demon.net
Tue Nov 2 03:36:30 PST 2004
Ken Murchison said:
>> But I'd certainly like to encourage extensions to indicate both what is
>> available and what is currently-unavailable, rather than just the former.
>> And this is something that I'd like to see even if we don't adopt this
>> STATUS proposal.
> I don't see why this is necessary. We really need client authors to
> weigh in here. We, as server authors shouldn't be deciding what's good
> for clients in a vacuum.
I'd still like to hear from client authors here.
>> Or we can bite the bullet and say that servers must advertise every command
>> that they implement.
> *Every* command? Why? The NNTPv2 capability states all of the base
> commands that the server supports (other than the optional LIST xxx
> stuff -- which is still a klugde IMHO). Any other commands MUST be
> advertised by an extension label.
Um, I didn't mean that each command should be listed separately in LIST
EXTENSIONS (or STATUS). I meant that every command supported (except for
the mandatory ones) should be *indicated* by something in the output. In
many cases several commands are indicated at once.
--
Clive D.W. Feather | Work: <clive at demon.net> | Tel: +44 20 8495 6138
Internet Expert | Home: <clive at davros.org> | Fax: +44 870 051 9937
Demon Internet | WWW: http://www.davros.org | Mobile: +44 7973 377646
Thus plc | |
More information about the ietf-nntp
mailing list