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

[Russ Allbery]

"Andrew - Supernews" <andrew at supernews.net> writes:

> However, the idea of returning a deferral in response to TAKETHIS (or
> indeed as the final response after IHAVE) is in any event logically
> somewhat flawed. The client in this case will always have sent the
> entire article body, and it is not reasonable to expect a client to do
> that repeatedly. Once the body is transferred once, the server has all
> the information needed to decide whether to accept or reject the
> article; transient errors at this point, such as "disk full", are better
> handled by pausing or throttling the server (without sending either 239
> or 439 to the client). Some implementations do actually return 431 in
> that case, but practical experience is that the resulting behaviour is
> never good (some senders will discard the articles, others will retry
> them indefinitely, potentially wasting large bandwidth volumes;
> throttling the server works much better).

So from a protocol standpoint, you believe the situations under which a
server might return a deferral to TAKETHIS or IHAVE are better handled by
just closing the connection without a response instead?

-- 
Russ Allbery (rra at stanford.edu)             <http://www.eyrie.org/~eagle/>