grpc: Add Timeout Support #525
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Subsystem
gRPC
Problem Description
To prevent the client from potentially waiting indefinitely for a server response, an important feature is the deadline. The deadline defines a specific point in time after which the client stops listening for responses from the server.
Solution
While some implementations employ the concept of Deadlines, others utilize Timeouts. Timeouts specify a Duration after the call starts, permitting its completion. Once the duration elapses, the call is terminated.
kotlinx.rpcalso uses Timeouts instead of Deadlines.Currently, call options can only be set by an interceptor. However, eventually users should be able to set them during service stub creation (KRPC-231).