Hi!
I need to figure out the internal code flow of iomgr in the case of a
client tcp connection. Could someone provided a rough guideline of what
happens when a new channel is created.
I am particularly interested in grpc 1.14, but I guess any recent version
would work as well.
Thanks!
--
Hi, just wondering if there is a good way to get the size of the message
instead of calling ByteSizeLong.
Concerned with performance issues...
Thanks!
--
You received this message because you are subscribed to the Google Groups
"grpc.io" group.
To unsubscribe from this group and stop
:02:07 AM UTC-7, grpc_client wrote:
>>
>> *Language*: C++
>> *gRPC version*: 1.2.5
>> *Role*: gRPC client
>>
>> A quick question here. I'm observing a situation where the client
>> attempts to connect to a server, repeatedly printing out the
*Language*: C++
*gRPC version*: 1.2.5
*Role*: gRPC client
A quick question here. I'm observing a situation where the client attempts
to connect to a server, repeatedly printing out the following error
(SOME_IP:PORT edited out)
[gRPC] watch_completion_error:
c/pull/16007
>
> On Thursday, July 12, 2018 at 8:06:05 AM UTC-7, grpc_client wrote:
>>
>> Thanks, I will try to check the ssl library we have.
>>
>> However, shouldn't the gRPC client work with an NPN response if it sends
>> the NPN request by itself?
>&
Hi,
I'm trying to establish a secure gRPC channel in a C++ based client. The
connection gets rejected with the following error message:
"Peer name A.B.C.D is not in peer certificate"
As far as I understand the expected peer_name is the ip of the server to
which the connection is being