Also see proposal https://github.com/grpc/grpc/issues/18204
On Thursday, February 28, 2019 at 3:32:27 PM UTC+8, Lei Wang wrote: > > It is much easier for us to implement coroutine in python, java, and > machines with VM so that we can monitor the memory address where we are > executing. > > in grpc c++, we recommend to use glib ucontext, which is widely employed > by our c++ developers and we could use it stop, consume threads for c++. By > deveoping Future so and wrapped async io event, we can jump back to memory > address where we wait for a task done. > > I would not recommend implementing async server completion queue callback > because it will be eventually replaced by a solution first released as the > coutine version async grpc. > -- 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/03338688-bf0f-4c58-bf56-690fffa97ea3%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
