I have a situation where I cancel a streaming RPC, upon which the client will return grpc::CANCELLED on reader->Finish(). However it does this directly because of the TryCancel on the client context, not because of the controller return of the RPC.
Since my RPC using an exclusive resource, only one client can be connected at time. Because of the early return on TryCancel, I can call the RPC again but it hasn't finished, so I get a grpc::RESOURCE_EXHAUSTED. I would like to be able to cancel an RPC, then wait until the RPC has "acknowledged" the cancellation, preferably by default gRPC methods. Regards /Robert -- You received this message because you are subscribed to the Google Groups "grpc.io" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/grpc-io. To view this discussion on the web visit https://groups.google.com/d/msgid/grpc-io/23027243-0722-4f80-a2ac-e46dfc4eecbe%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
