🚀 go-pugleaf

In article <905708234.18272.0.nnrp-05.d4e48b20@news.demon.co.uk>,
Alisdair Wren <alisdair@nospam.demon.co.uk> writes

>While I'm about it, I was retrieving a list of newsgroups, and all of a 
>sudden the server came out with "503 Internal program fault".  What it 
>did not, however, do is a <CR-LF>.<CR-LF> before saying that.

that's sad (and indeed "broken")

>  Although 
>this line could be recognised not to be a LIST line, if this occurred in 
>a message, this could not be trapped by the news client as an error.  
>How would you propose dealing with such an eventuality?

by applying tolerance {or as the RFC would have it; being "liberal"} :)

>  I was 
>considering putting up a message upon unexpected connection termination 
>during textual output, stating merely that unexpected disconnection had 
>occurred, and quote the last line given by the server.

a reasonable solution

-- 
richard                       writing to inform and not as company policy
 http://www.demon.net/news/features/crypto/  for Demon's views on crypto
"Assembly of Japanese bicycle require great peace of mind" quoted in ZAMM