Documentation of new LIST commands
Julien ÉLIE
The NNTP specification [RFC3977] defines the LIST capability and a
few keywords which can be used with that command: ACTIVE,
ACTIVE.TIMES, DISTRIB.PATS, HEADERS, NEWSGROUPS, and OVERVIEW.FMT.
As other widely used variants of the LIST command currently exist,
it would be great to document them.
I have just posted proposals for:
* LIST DISTRIBUTIONS
* LIST MODERATORS
* LIST MOTD
* LIST SUBSCRIPTIONS
Do you see other existing LIST commands that should also be documented?
Do you see something that would be worthwhile having in a LIST command?
(and which currently does not exist)
I submitted that in an Internet-Draft:
http://www.ietf.org/internet-drafts/draft-elie-nntp-list-additions-00.txt
--
Julien ï¿œLIE
ￜ -- Par Jupiter !
-- Par Toutatis !
-- Par pitiￜ ! ￜ (Astￜrix)
D. Stussy
news:he74q9$58m$1...@news.trigofacile.com...
> Hi,
>
> The NNTP specification [RFC3977] defines the LIST capability and a
> few keywords which can be used with that command: ACTIVE,
> ACTIVE.TIMES, DISTRIB.PATS, HEADERS, NEWSGROUPS, and OVERVIEW.FMT.
> As other widely used variants of the LIST command currently exist,
> it would be great to document them.
>
> I have just posted proposals for:
>
> * LIST DISTRIBUTIONS
> * LIST MODERATORS
> * LIST MOTD
> * LIST SUBSCRIPTIONS
>
>
> Do you see other existing LIST commands that should also be documented?
>
> Do you see something that would be worthwhile having in a LIST command?
> (and which currently does not exist)
>
>
> I submitted that in an Internet-Draft:
>
http://www.ietf.org/internet-drafts/draft-elie-nntp-list-additions-00.txt
>
Perhaps identification of which lists are available only in "reader mode?"
After all, INN only seems to implement ACTIVE and NEWSGROUPS in peer mode
(at least that's what I seem to remember). The rest are present only in
the nnrpd program, not innd.
Julien ÉLIE
>> Do you see something that would be worthwhile having in a LIST command?
>> (and which currently does not exist)
>
> Perhaps identification of which lists are available only in "reader mode?"
> After all, INN only seems to implement ACTIVE and NEWSGROUPS in peer mode
> (at least that's what I seem to remember). The rest are present only in
> the nnrpd program, not innd.
I do not understand well your request. Isn't what CAPABILITIES is for?
The LIST capability shows which lists are available. You would have wanted
innd to tell which lists nnrpd knows?
What's the need behind that request?
200 news.trigofacile.com InterNetNews server INN 2.6.0 (20091107 prerelease) ready (transit mode)
CAPABILITIES
101 Capability list:
VERSION 2
IMPLEMENTATION INN 2.6.0 (20091107 prerelease)
AUTHINFO
IHAVE
LIST ACTIVE ACTIVE.TIMES NEWSGROUPS
MODE-READER
STREAMING
.
MODE READER
200 news.trigofacile.com InterNetNews NNRP server INN 2.6.0 (20091107 prerelease) ready (posting ok)
CAPABILITIES
101 Capability list:
VERSION 2
IMPLEMENTATION INN 2.6.0 (20091107 prerelease)
AUTHINFO USER SASL
HDR
IHAVE
LIST ACTIVE ACTIVE.TIMES DISTRIB.PATS HEADERS NEWSGROUPS OVERVIEW.FMT
OVER
POST
READER
SASL GSSAPI OTP PLAIN NTLM LOGIN DIGEST-MD5 CRAM-MD5
STARTTLS
.
QUIT
205 Bye!
--
Julien �LIE
� Plus un ordinateur poss�de de RAM, plus vite il peut g�n�rer un message d'erreur. �
D. Stussy
> >> Do you see something that would be worthwhile having in a LIST
command?
> >> (and which currently does not exist)
> >
> > Perhaps identification of which lists are available only in "reader
mode?"
> > After all, INN only seems to implement ACTIVE and NEWSGROUPS in peer
mode
> > (at least that's what I seem to remember). The rest are present only
in
> > the nnrpd program, not innd.
>
> I do not understand well your request. Isn't what CAPABILITIES is for?
> The LIST capability shows which lists are available. You would have
wanted
> innd to tell which lists nnrpd knows?
> What's the need behind that request?
The fact that different parts of the software package offer different
capbilities may be significant to some other package.
As noted, not all LIST options are supported by innd but are supported by
nnrpd; the difference being whether a client has issued "MODE READER".
That is, capabilities may change based on prior commands issued.
Julien ÉLIE
> As noted, not all LIST options are supported by innd but are supported by
> nnrpd; the difference being whether a client has issued "MODE READER".
>
> That is, capabilities may change based on prior commands issued.
Commands like "MODE READER", "AUTHINFO" or "STARTTLS" may change
the capabilities list.
That's normal, and a client should expect that.
--
Julien �LIE
� Pour d�fendre une cause, un avocat met sa robe. Une femme... l'enl�ve. �
D. Stussy
> > As noted, not all LIST options are supported by innd but are supported
by
> > nnrpd; the difference being whether a client has issued "MODE READER".
> >
> > That is, capabilities may change based on prior commands issued.
>
> Commands like "MODE READER", "AUTHINFO" or "STARTTLS" may change
> the capabilities list.
> That's normal, and a client should expect that.
But should one be reminded of it here?