Hi,
If using the callback API, you wouldn't need to create a separate thread
for each RPC. The callbacks in the reactor would be automatically invoked
by the threads managed by the gRPC library. That being said, if the reactor
is going to be blocking for a substantial amount of time, you would
Absolutely, I'll reach out when the EventEngine integration is a bit more
feasible. As Mark said, getting to a point where gRPC is ready for custom
EventEngine integration is maybe 6 months away.
The EventEngine API is public, you can review and comment on it
here:
(Adding AJ, who's driving the EventEngine effort.)
AJ, it looks like Sureshbabu wants to be an early tester of the new
EventEngine code on Windows. Please coordinate with him when we get to a
point where the new code is actually ready for testing (specifically the
client-side endpoint code).
On
In our intranet, GRPC servers are running in different computers. While
many of the servers are connecting without any issue, there are some
servers failed with error *"DNS resolution failed for service :
:"*
The issue can be resolved by adding the environment variable
*GRPC_DNS_RESOLVER*
