Completion queues can be shared among multiple clients. Yes, for shutdown, yes you got the sequence right
On Thursday, March 22, 2018 at 11:15:13 AM UTC-7, Todd Defilippi wrote: > > I have a number of async clients that are connecting to services on > multiple async servers. Should each client have its own completion queue > or does it need to be shared among all clients? (Or are both allowable and > it's a design choice?) > > On a related note, I'm trying to pin down the correct sequence for > shutting everything down. I believe it is: > - Tear down all client connections (delete stub, reader, etc.). > - Call Shutdown on the completion queue. > - Drain the completion queue of any remaining events. > - Destroy completion queue. > > Is that right? > > Thanks, > Todd > -- 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/e11a1dad-fde7-4c4d-9601-f35a0c85f6c8%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
