> We've been talking this topic many times.
> The RFCs say that the server has to close the
connection, so if
> a server doesn't close the connection on receiving
command QUIT
> the server is buggy. You can handle those
server-side bugs with a simple
> command timeout, in real applications some a
timeout mechanism is required
> anyway.
I agree with Arno: breaking the connection after the
QUIT command without closing it normally, breaks RFC
compliancy and is a bug.
Sometimes it is a good idea to modify the components
to handle common idiosyncracies of servers that are
common, in order to make it more robust. However, in
this case, a simple timeout event, as recommended,
would correct your problem; and since it is a good
idea to implement a command timeout on networking
applications anyway, it is not necessary to modify
the component to handle this issue.
-dZ.
--
To unsubscribe or change your settings for TWSocket mailing list
please goto http://www.elists.org/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be
