ietf-nntp LIST EXTENSIONS non-pipelined and non-cacheable?

[Clive D.W. Feather]

Peter Robinson said:
> | 5.3 LIST EXTENSIONS
> 
> | This command MUST NOT be pipelined.
> 
> Why not?

Um, I don't remember.

Looking back, we discussed this in January 2002 and the only good reason
that came up was that a server might load modules or do something strange
in response to LIST EXTENSIONS.

But if we're taking the view that LIST EXTENSIONS shouldn't change the
server state, merely document it (a view that I agree with) then there's no
reason not to make it pipelineable.

So I'm in favour of this change.

> | An NNTP client MUST NOT cache (for use in another session)
> | any information returned if the LIST EXTENSIONS command succeeds.
> It seems inconsistent that on one hand, a client can (try to) use an
> extension having no idea whether it's supported, while on the other hand
> it is forbidden to cache the LIST EXTENSIONS response, and use it to
> make an educated guess.
> 
> I'd have thought that that kind of decision should be left to newsreader
> authors and users.  So 

This is a separate topic which I'd like to discuss.

-- 
Clive D.W. Feather  | Work:  <clive at demon.net>   | Tel:    +44 20 8495 6138
Internet Expert     | Home:  <clive at davros.org>  | *** NOTE CHANGE ***
Demon Internet      | WWW: http://www.davros.org | Fax:    +44 870 051 9937
Thus plc            |                            | Mobile: +44 7973 377646