ietf-nntp Draft 17 pre-2
Clive D.W. Feather
clive at demon.net
Mon Mar 3 01:49:10 PST 2003
Ken Murchison said:
>> Code option 1:
>>
>> * Call LIST EXTENSIONS
>> * Check for 202 return code
>> * Check output for OVER
>> * Set a flag
if OVER present
>> * As required:
>> * If flag set:
>> * Call OVER
>> * Check for 224 versus 423 versus 503
>>
>> Code option 2:
>>
>> * As required:
>> * Call OVER
>> * Check for 224 versus 423 versus 500
> I would hope that if you get a 500, that you'd set a flag so that you
> don't keeping asking for OVER even though the server tells you that you
> its doesn't support it.
Indeed.
>> Code option 2bis:
>>
>> * Set a flag
>> * As required:
>> * If flag set:
>> * Call OVER
>> * Check for 224 versus 423 versus 500
Same comment.
> There *are* reasons why POP3, IMAP, and SMTP have extension discovery
> commands, and clients *use* them.
POP3 does?
Which reminds me - why *is* RFC 1939 cited in the draft?
--
Clive D.W. Feather | Work: <clive at demon.net> | Tel: +44 20 8371 1138
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 | |
More information about the ietf-nntp
mailing list