[NNTP] draft-ietf-nntpext-streaming-02

[Ken Murchison]

Andrew - Supernews wrote:

> INN never generates 436 after receiving an article body. Older diablo
> versions (haven't checked newer ones) generate 436 if they failed to
> store the article, which is bogus for the same reasons that I covered
> for the TAKETHIS case (it results in the sending end wasting a lot of
> effort).
> 
>  Clive> If they do, why shouldn't they generate 432 in the same
>  Clive> situation?
> 
> I assume you mean "431" rather than "432", because generating 432
> under any circumstances whatever breaks existing streaming clients.
> 
> Every implementation I've checked handles article bodies in IHAVE
> and TAKETHIS commands the same, generally using the same code.

So, are you saying that in practice that servers will never (and should 
not ever) respond with a deferral type code to IHAVE, POST, and TAKETHIS 
after receiving the article?

-- 
Kenneth Murchison     Oceana Matrix Ltd.
Software Engineer     21 Princeton Place
716-662-8973 x26      Orchard Park, NY 14127
--PGP Public Key--    http://www.oceana.com/~ken/ksm.pgp