When a server-side computaion takes long time that exceeds the given timeout of the client, RcfError_ClientReadTimeout error will be raised.
I think in that scenario, we can resuse a the existing TCP connection.
But, why does RCF disconnect it?
why disconnect on error: RcfError_ClientReadTimeout?
Re: why disconnect on error: RcfError_ClientReadTimeout?
In a timeout situation it's no longer known what state the connection is in (e.g. was the request dropped on the network? Or is the request still being processed on the server? Or was the response dropped on the network?). So to get things back to a known state, we close the connection and open a new one.