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

2024-05-23 Thread Guruprasad Shettigar
is there any easy-to-understand example for a multithreaded c++ grpc server which handles multiple client requests, regards, guru On Wednesday, June 16, 2021 at 10:52:19 PM UTC+5:30 yas...@google.com wrote: > > However, HandleRpc() only call proceed() once,. It seems we always stay > in the

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

2021-06-16 Thread 'yas...@google.com' via grpc.io
> However, HandleRpc() only call proceed() once,. It seems we always stay in the PROCESS state. Will it generate the memory leak? No, the same CallData object is used multiple times as a completion queue tag, allowing the state to progress. > What does it mean to have cq->next(, ) return the

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

2021-05-30 Thread Mohan Gyara
What does it mean to have cq->next(, ) return the out param ok as false? I appreciate if someone answer this. Regards, Mohan On Thursday, 5 November 2015 at 08:48:33 UTC+5:30 hardy wrote: > Is there anyone familiar with CompleteQueue could tell me how the > mechanism is? The only piece of

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

2019-03-15 Thread dalin5168
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