Problem Description
Lifetimes in kRPC were not well handled, which led to leaks and undefined behavior.
Solution
This PR introduces cancellation mechanism, which has three levels: request, service and endpoint. Each of these entities can be cancelled and cancellation notice will be sent to a peer endpoint. Cancellation cases are handles according to the design doc.
This PR covers cases of plain requests, excluding streamings, though providing base for further work with streams.
As PR is quite big, it is divided into 3 main parts (by commits):
Problem Description Lifetimes in kRPC were not well handled, which led to leaks and undefined behavior.
Solution This PR introduces cancellation mechanism, which has three levels: request, service and endpoint. Each of these entities can be cancelled and cancellation notice will be sent to a peer endpoint. Cancellation cases are handles according to the design doc.
This PR covers cases of plain requests, excluding streamings, though providing base for further work with streams.
As PR is quite big, it is divided into 3 main parts (by commits):