Thanks for moving this discussion here Vijay, definitely the better place.

A couple of comments about your notes

> We are moving toward providing an iomgr in OSS that will allow callbacks to 
> be triggered in a separate threadpool independently of application control.

I'm not really aware of the concurrency model used by the C++
implementation - any link that its worth it to take a look will be
welcomed. But regarding your comments about the substantial change
that will imply a modification that will allow executing the callbacks
in a thread pool, remember that wrappers such as the Node.js one or a
future implementation for Asyncio won't need that which are based on
loop reactors where the callbacks are executed in the same thread. So,
I'm wondering if even being an experimental implemetnation it's in a
certain way ready to be used in scenarios where the concurrence is
achieved in another way.


> It may become possible to consider using this in other language bindings as 
> well and perhaps it could be suitable for interfacing with another async 
> library; that is an interest of ours but not a priority so we'd certainly 
> welcome any input or contributions.

Regarding the Asyncio implementation, there is a lot of work to be
done and most probably many unknowns that have to be discovered and
circunvented. So, Im not worried about the experimental situation of
the callback completion queue, most probably if eventually, the
Asyncio binding becomes something real the time needed to so will be
enough to see this experimental change into something stable.


Thanks!

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

Reply via email to