This is something that we can definitely consider as a grpc-ecosystem contribution but we are trying to keep the core of grpc C++ relatively more basic since the use cases are so diverse. I have filed an issue at https://github.com/grpc/grpc/issues/7352 .
On Friday, July 8, 2016 at 10:32:50 AM UTC-7, Ming Zhao wrote: > > Greetings! > > I'm just curious to know whether there is any future plan to improve > grpc C++ asynchronous API. > > Frankly speaking, I'm a little shocked when taking the first glance at > that API. Don't you feel there is a little more than necessary > boilerplate and indirection there? Shouldn't this be hidden in a > different API other than letting the user deal with the tedious > dispatching there? I guess maybe a little more generalized default > dispatcher could save a lot of learning effort here. > > Thanks, > Ming > -- 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/grpc-io/600c0c18-128e-44ab-a934-5c8d49adfc23%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
