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/CAN0GiO0AM6ORGtbjwg2_yB_fU3KO3bSS7Epz%3D18UykVHc_QQbg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to