if the RPC message isn't completely sent, it still sends until the end
the server is not notified that the RPC is cancelled, and thus still handles it
if the request is already produced and is being sent, it is sent until the end
What we would want to happen instead, when a RPC caller cancels their call (i.e. when the .call() future is dropped), is the following:
transmission of request stops ASAP
remote is informed of cancellation, it should not send response if it is produced
if response was being sent, cancel sending it
Currently, when a RPC caller cancels their call,
- if the RPC message isn't completely sent, it still sends until the end
- the server is not notified that the RPC is cancelled, and thus still handles it
- if the request is already produced and is being sent, it is sent until the end
What we would want to happen instead, when a RPC caller cancels their call (i.e. when the `.call()` future is dropped), is the following:
- transmission of request stops ASAP
- remote is informed of cancellation, it should not send response if it is produced
- if response was being sent, cancel sending it
Currently, when a RPC caller cancels their call,
What we would want to happen instead, when a RPC caller cancels their call (i.e. when the
.call()future is dropped), is the following:Fixed I don't remember when