Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!wuarchive!brutus.cs.uiuc.edu!coolidge From: coolidge@brutus.cs.uiuc.edu (John Coolidge) Newsgroups: news.software.nntp Subject: Re: "maybe-I-have" (Re: Lots of dups) Message-ID: <1989Oct29.221102.28084@brutus.cs.uiuc.edu> Date: 29 Oct 89 22:11:02 GMT References: <1989Oct25.164024.14894@ctr.columbia.edu> Sender: news@brutus.cs.uiuc.edu Reply-To: coolidge@cs.uiuc.edu Organization: U of Illinois, CS Dept., Systems Research Group Lines: 27 flee@shire.cs.psu.edu (Felix Lee) writes: >John Coolidge wrote: >> It's in the NNTP spec, more or less. Just use NNTP response code 436 >> (transfer failed - try again later). >Except that when "nntpxmit" gets a "436" it aborts the rest of the >transfer. "436" is used by "nntpd" when "rnews" fails, and when that >happens, it's often pointless to keep sending things to have "rnews" >fail again. ACK! Well, I _said_ I wasn't sure that current software handled it correctly! :-) >Some distinction should be made between this-article failure and >news-system failure. You're right, of course. We seem to need a new response code for NNTP to handle this, since the existing one has been used to deal with a different class of errors. --John -------------------------------------------------------------------------- John L. Coolidge Internet:coolidge@cs.uiuc.edu UUCP:uiucdcs!coolidge Of course I don't speak for the U of I (or anyone else except myself) Copyright 1989 John L. Coolidge. Copying allowed if (and only if) attributed. You may redistribute this article if and only if your recipients may as well.