Re: [grpc-io] Server and client completion queue

Should we call CallData::Proceed() twice to avoid the memory leak?? The first call is to change from the PROCSS state to FINISH state and the second call is to free the memory itself. Thanks, David On Friday, November 3, 2017 at 8:20:38 AM UTC-7, Sree Kuchibhotla wrote: > > The async server he

Re: [grpc-io] Re: What is the mechanism of Completion Queue?

In Proceed(), there are three states {CREATE, PROCESS, FINISH}. In the FINISH state, we free the memory of CallData. However, HandleRpc() only call proceed() once,. It seems we always stay in the PROCESS state. Will it generate the memory leak? On Tuesday, January 26, 2016 at 4:53:38 PM UTC-8,

Re: [grpc-io] Python gRPC cancel unary-stream call from client side

Easy, thanks very much. I should have looked at the code for the _Rendezvous object, rather than getting frustrated with the documentation. On Friday, 15 March 2019 08:26:59 UTC+1, Lidi Zheng wrote: > > Can you try “stream.cancel()”? The “cancel()” method is available for both > client conte

[grpc-io] client only in c#

Is there a way to create a client only dll which doesn't contains the server implementation. Because in the sample from github when you build the solution it creates a HelloWorldGrpc.cs file with all the stuff in one namespace which is needed for both client and server. What i want is a separat

Re: [grpc-io] Python gRPC cancel unary-stream call from client side

Can you try “stream.cancel()”? The “cancel()” method is available for both client context and server context. See *class *grpc.*RpcContext in * *https://grpc.io/grpc/python/grpc.html#client-side-context .* On Thu, Mar 14, 2019 at 23:54 Mar