Oh, I didn't realize your grpc java version was so old. Good to know your
issue is resolved.
On Fri, Aug 25, 2023 at 1:23 AM '邹会江' via grpc.io
wrote:
> Thanks！
> I upgrade the grpc-java version from 1.3.3 to 1.51.0, and the IDLE time is
> reduced from 1000ms to 300ms.
>
> 在2023年8月25日星期五 UTC+8
Thanks for example, but I have one doubt in Client code:
call->response_reader = stub_->AsyncSayHello(>context, request, _,
(void *)call);
What if we receive response in bool HandleResponse(bool responseStatus)
before call->response_reader is assigned. Isn't it potential racing
condition?
I have been working with gRPC 1.43.0 and tried today to upgrade to 1.57.0.
However, when I try to build for debug, the cares submodule doesn't compile
because the types "struct ares_addrinfo", "struct addrinfo_node", and
"struct addrinfo_cname" are not defined. Here are a couple of sample error
https://github.com/grpc/proposal/pull/391 is a gRFC for defining a new API
for the Node gRPC health check library.
Feedback welcome.
--
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,
I'm not sure exactly how, but my suspicion is that you are somehow picking
up an old `ares.h` on your include path.
For what it's worth, we upgraded the c-ares dependency to 1.19.1 starting
on the 1.56 release (see https://github.com/grpc/grpc/pull/33411).
At that version, note that
Thanks！
I upgrade the grpc-java version from 1.3.3 to 1.51.0, and the IDLE time is
reduced from 1000ms to 300ms.
在2023年8月25日星期五 UTC+8 13:05:56 写道：
> Instead of modifying and using the jre/lib logging.properties file can you
> try using one for your application alone as described in my previous
