Attached tiny patch to XmlRpc++ 0.7 always asks for
exceptions in XmlRpcClient::handleEvent as per the
comment that it should probably be done. This changes
makes difference when the server stops or closes the
connection and the client tries to send new request:
because XmlRpcClient is using select() to wait until it
can write to the socket and ignores exceptions, it will
never learn that the peer is no longer acception data.
After applying this patch, the client will receive
exception (assuming the connection was closed
correctly) and will immediately return with error
instead of hanging indefinitely, as it does now.
Log in to post a comment.