I've noticed that Grpc.Auth was intentionally not included in Unity support.
The commit below does read that it was temporarily excluded (to make
something else work, presumably):
Commit: 911d7779bcf4b986f31e4d465b6d977275459b70 [911d777]
> Parents: 6574f5def4
> Author: Jan Tattermusch
> Date:
Hi Yilun,
What do you mean by free the service? Since I am trying to use this as CLI
I am not freeing any service. If you mean that I have to free the
"GetResponseMsg" that I get back as a response then can you please let me
know how to do that?
Thanks,
Srikanth
On Thursday, March 7, 2019 at
Hm, what you did was exactly right.
In our example, here's how we passed "custom-header-1" (deliberately as an
example on how to pass custom metadata)
envoy.yaml:
https://github.com/grpc/grpc-web/blob/master/net/grpc/gateway/examples/echo/envoy.yaml
client:
https://github.com/grpc/grpc-web/blob/ma
As far as I remember, we elegantly dismissing the message, and everything
looks like working. Just make sure you really finish all outstanding stuff
in the queue
On Friday, March 22, 2019 at 2:58:35 PM UTC+2, seazo...@gmail.com wrote:
>
> Hi,ernest
> have solved this problem? i got the same mess
Hi,ernest
have solved this problem? i got the same message.
在 2018年7月31日星期二 UTC+8上午1:16:10，ernest.w@gmail.com写道：
>
> Thats it, I'm counting operations and dont see how anything could be
> pending in the queue. If I break the loop on destruction and destroy
> objects I get following cryptic
So with this setup you still need to transmit the certificate from the
client to the server ?
I'm a bit confused with the example because earlier you said "No need for
client certificate." Is this root certificate (the "roots.pem" file)
generated by the server and then given to the client someh
