ietf-nntp Section 7.1 - GREETING step.
Charles Lindsey
chl at clw.cs.man.ac.uk
Wed Jul 26 01:38:08 PDT 2000
In <200007251708.KAA08690 at karoshi.ucsd.edu> Brian Kantor <brian at UCSD.Edu> writes:
>>If, as far as the server can determine at the point of connection,
>>neither IHAVE nor POST will be permitted during this session, the
>>server returns a 201 response. Otherwise it returns a 200 response.
>>Can everyone live with that ?
>No, I think this is seriously flawed. If a server returns a 200
>but a subsequent POST fails, you've screwed the client. 201 indicates
>ONLY the usability of the POST command.
Well a logical solution would be to say
200 you may only read
201 you may POST
202 you may IHAVE
203 you may do BOTH
Given that in practical situations clients are usually either in the
reading business or in the relaying business, but rarely in both, what
current clients would actually get confused if servers suddenly started
behaving like that?
--
Charles H. Lindsey ---------At Home, doing my own thing------------------------
Email: chl at clw.cs.man.ac.uk Web: http://www.cs.man.ac.uk/~chl
Voice/Fax: +44 161 437 4506 Snail: 5 Clerewood Ave, CHEADLE, SK8 3JU, U.K.
PGP: 2C15F1A9 Fingerprint: 73 6D C2 51 93 A0 01 E7 65 E8 64 7E 14 A4 AB A5
More information about the ietf-nntp
mailing list