No, that's not easy. gRPC expects a single socket for reading and writing.
On Thu, May 2, 2019 at 12:07 PM Antonio Goncalves
wrote:
> Hi Everyobody,
>
> how are you doing?
>
> I'm not so familiar with the high levels of gRPC, as I work in a more HW
> level. I'm trying to integrate the gRPC
Thanks Carl . If you find something, pls let us know.
Regards
Anurag
On Wednesday, May 1, 2019 at 5:04:35 PM UTC-4, Anurag Misra wrote:
>
> Hi Friends,
>
> We have gRPC server which receives the request, and based upon one
> specific validation, we want to return the request without sending it
I haven't personally run with it, but there is active development from
Google on Envoy, so it typically has good support. Any of those with Envoy
support would be what I would look at first. (again, taking into account
my inexperience).
On Tuesday, April 30, 2019 at 2:54:01 PM UTC-7,
You can turn on keep alives on the channel / server builder, but that's
about the best you can do. The problem is that a broken connection just
means silence. You can't tell the difference between the packets taking a
long time, and the the packets not arriving. Keep-alives let you check the
Yes this seems to solve the problem, but the comments say:
>
> should never be used in production
What is the reason?
Is this option unsafe or unstable?
Thanks
Guido
On Wednesday, May 1, 2019 at 7:21:39 PM UTC+2, Muxi Yan wrote:
>
> This is probably what you are looking for:
>