ietf-nntp Concerning Streaming

[Clive D.W. Feather]

greg andruk said:
>> I don't understand why people want POST to be not streamable.
> It's not a matter of wants, but of recognizing existing implementations =(

That's what I meant.

> [...]
>>     [C] Test text
>>     [C] .
>>     [C] DATE
>>     [S] 240 posting accepted
>>     [C] GROUP misc.test
>> 
>> can the client rely on receiving a 111 line next, or is it possible that
>> the server threw away the DATE command, so that the next response will be
>> the 211 ?
> 
> Yes, it's possible.  NNTP 1.5.x forks and execs inews on each POST.
> If batching is not copmiled in,  it does the same with rnews on IHAVE.

Okay, so in that case these commands can't be streamable.

>> I seem to recall there was a belief that LIST EXTENSIONS might kick in a
>> new invocation of the server with extra modules loaded. Hence the desire to
>> make it non-streamable.
> I can see where the available extensions could easily differ before and
> after, say, a MODE command, but for the LIST itself to be cause for a new
> process seems odd.  Was that idea maybe be a holdover from the old proposal
> to change AUTHINFO's return codes from x8x to x5x if a LIST EXTENSIONS was
> seen?

I don't think so. But this point about loading modules is the only reason I
can think of for making it not streamable.

-- 
Clive D.W. Feather  | Work:  <clive at demon.net>   | Tel:  +44 20 8371 1138
Internet Expert     | Home:  <clive at davros.org>  | Fax:  +44 20 8371 4037
Demon Internet      | WWW: http://www.davros.org | Mobile: +44 7973 377646
Thus plc            |                            |