Re: Client action in response to a PARSE response code

[Perry Ruiter]

Arnt Gulbrandsen write:
>A tagged NO means something is wrong with that command.  An untagged BYE 
>ALERT means that the server is closing the connection and requests that 
>the user be alerted.
  A tagged BAD means something is wrong with the command.  A tagged
NO says there was an error processing the command.  I can always send
an ALERT on a tagged BAD.
  Frankly, I was surprised when Mark said that FETCH should never 
return a tagged NO and that the preferred approach was to dummy
up a note's structure when running into difficulty.  I sure didn't
get that from reading the RFC.
  I'm equally surprised at the rush to * BYE a client at the
slightest hint of a problem.  I guess I was naive to assume that 
clients might have enough intelligence to take alternate action
if exposed to the full spectrum of the protocol ... Perry