[NNTP] Snapshot 5

[Clive D.W. Feather]

Russ Allbery said:
>> You don't see the benefit in the example?
>>   [C] CAPABILITIES
>>   [S] 101 Capability list:
>>   [S] VERSION 2
>>   [S] READER
>>   [S] LIST ACTIVE NEWSGROUPS
>>   [S] (test-version-2.1) STREAMING
>>   [S] .

> What bothers me about this example is that the first time I read it, I
> thought "oh, that means that the server is sort of supporting the
> STREAMING extension but hiding it from any client so that a client won't
> try it yet, since it's experimental."  It was only after reading the text
> that I realized that it was supposed to be treated as equivalent to
> advertising STREAMING, which I found really counter-intuitive.

Oh, I see what you're getting at.

> I just don't think there's enough use in this to have it be worth it.

Okay. It's gone.

>>> Should OVERVIEW.FMT and HEADERS really be listed as LIST arguments? 
>>> Both of these LIST variants are governed by their own capabilities
>>> (OVER and HDR respectively).  Its seems kind of crufty that a single
>>> command like LIST HEADERS would have both a separate capability (HDR)
>>> and an argument to a second capability (LIST) to advertise it.
>> Opinion on this matter seems to be split. It's also why I wanted to
>> rename LIST HEADERS as something else.
> I'm not sure what to do about this.  We can't rename LIST OVERVIEW.FMT, so
> the problem is going to exist no matter what we do.

Indeed.

-- 
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            |                            |