[NNTP] Revisiting POST as a separate capability

Russ Allbery rra at stanford.edu
Fri Mar 25 09:59:33 PST 2005


Clive D W Feather <clive at demon.net> writes:

> But here I don't. Having LISTGROUP without READER doesn't make sense.
> Therefore it is far better to implement the restriction by making
> LISTGROUP be an argument to the READER capability than to have to
> special-case it in the text.

The problem with this is that if we ever want to add the range argument to
LISTGROUP later on (since it's looking like specifying this may involve
more details than we want to deal with at this stage), you end up with a
very ugly way of specifying that in capabilities.

It also then looks odd.  We would be leaving LISTGROUP as the only command
capability that isn't its own line in CAPABILITIES.  (That's more of an
aesthetic argument, though, and isn't as strong.)

-- 
Russ Allbery (rra at stanford.edu)             <http://www.eyrie.org/~eagle/>



More information about the ietf-nntp mailing list