Re: [grpc-io] How to set source ip address in grpc client application

Hi, Is there way in grpc to bind to source ip address. In scenario of multiple physical ecmp interface to reach server it's better to use loopback interface source ip. Thanks, Deepak On Wednesday, October 18, 2017 at 8:43:09 AM UTC-7, Nathaniel Manista wrote: > > On Wed, Oct 18, 2017 at 12:05

Re: [grpc-io] grpc Dial behavior

It is a persistent connection. But if you only have one backend (or, more importantly, one hostname, such as behind a hardware load balancer and/or proxy), the client does not create redundant connections. So there is some downtime while it re-creates a socket connection after it gets

[grpc-io] Non-blocking single-threaded streaming C++ server

I am trying to write a streaming server as part of implementing a gRPC dial-out collector for Cisco's model-driven telemetry (https://github.com/cisco/bigmuddy-network-telemetry-proto/blob/master/proto_archive/mdt_grpc_dialout/mdt_grpc_dialout.proto). Is there a way to create the gRPC server

[grpc-io] grpc Dial behavior

Hi, I have a question regarding the grpc Dial behavior. I have a server, which as part of the incoming request needs to talk to another endpoint using grpc. Currently, on the server spawn, it does grpc.Dial to the other endpoint. and when the request comes, it does a grpc on this

[grpc-io] Re: Why endpoint_pair are piped?

Thanks Ken. So, it is probably useful for quickly prototyping application logic or write some quick tests for the new applications ? As a piped pair of endpoints will eliminate the need of a separate external grpc server(or client). On Thursday, February 22, 2018 at 12:24:03 AM UTC+5:30, Ken