> Shouldn't the exception be logged even if the socket is null ?
No. NNTP clients often leave sockets open for extending periods of time
without closing or using them. We time them out regularly, as some of our
users have noticed. We log the fact that we timed out the socket.
Gratuitiously forcing and logging an exception that we would be responsible
for causing is a poor practice.
> It is good to check for socket != null, but
> try {
> doQUIT(null);
> } catch(Throwable t) { }
> Would be effective even if it is socket is null.
Excuse me? How precisely are you proposing to send a message through a
socket whose instance is null? Please define "effective."
--- Noel
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
