[NNTP] [2501] Reader commands in transit servers and vice-versa

[Clive D.W. Feather]

Richard Clayton said:
> I suspect that a "reader only" configuration will allow POST (but may
> not allow IHAVE).
> 
> This is confusing because POST is "writing" ... so I think its a dumb
> name (based on old concepts) to put into a new spec :(

So you think that we shouldn't use the term "reader", but don't actually
think we should change the specification other than by changing this word?

Other opinions? I don't like "customer", but can we find a perhaps-less
confusing name?

> A new point (which I hope I can express clearly): "end-user" systems (as
> opposed to transit servers run by ISPs) usually use POST, but sometimes
> use IHAVE...  making servers fully implement everything in order to
> accommodate legacy users of IHAVE doesn't seem likely -- so I expect one
> will see "reader only" systems with extensions to cope with IHAVE.

At present IHAVE is the *only* transit command, so that would actually be a
general-purpose server.

In case we ever have more transit commands in the core specification, do we
want a separate capability for IHAVE? Or do we see this (IHAVE but not
other transit commands) as an unlikely enough case to ignore?

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