Writes still use the old rpc_timeout
Changed to getWriteRpcTimeout()
looks like most remaining uses of old rpc_timeout should really be max(different timeouts)
wanna modify the getRpcTimeout in DD so that it returns the max of the other get*RpcTimeout()?
currently, expiring map checks callbacks for expiration every 1/2 of default timeout. This means short timeouts could go much longer than desired, before being cancelled. I see two options: go back to direct await(timeout) in the callback/response handlers, or update EM to scan much more frequently (which could burn a lot of CPU for a system with many outstanding callbacks)
Not a so elegant solution in this patch. It uses the corresponding get*RpcTimeout in different callbacks.