> Richard alread stated that the client does not expect a response from the
> server, so calling ReadLn() is not the correct thing to do on the client
> side. There are only 1 place in his client side that the exception could
> be
> occuring, and that is on the WriteLn(). Since the server is calling
> ReadLn(), there should be no reason for WriteLn() to be called after the
> server has disconnected the socket, except under two possible conditions:
Sorry! - I was only trying to show another way of getting around the
"connection closed gracefully" thing. I know what a pig it can be.
Besides, Richard stated that he currently disconnects the client FROM the
SERVER. Therefore, maybe he will actually find my tip useful? - Maybe he
WANTS to disconnect from the server.
Jamie
