Handle cancellation correctly #5

Closed
opened 2022-08-31 15:11:58 +00:00 by lx · 1 comment
Owner

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, - 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
Author
Owner

Fixed I don't remember when

Fixed I don't remember when
lx closed this issue 2023-01-31 22:43:19 +00:00
Sign in to join this conversation.
No Label
No Milestone
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: lx/netapp#5
No description provided.