On Tue, Mar 6, 2018 at 3:59 PM, wrote:
> The true vs false on getState was still a mystery. As you indicate it
> never did anything for me. I think if it was working it would be
> beneficial. What I'm trying to achieve was prioritize which endpoints are
> most likely to
Thanks for the responses. I basically figured most of that state table
just by playing some with it :)
The true vs false on getState was still a mystery. As you indicate it
never did anything for me. I think if it was working it would be
beneficial. What I'm trying to achieve was
On Mon, Mar 5, 2018 at 11:16 AM, wrote:
> Thanks .. So when I bring down the remote server Current state goes from
> READY to IDLE . the channel stays in shutdown terminated both to false.
> It seems to stay that way.
>
On Mon, Mar 5, 2018 at 11:28 AM,
Here's a document that describes the allowed state transitions
https://github.com/grpc/grpc/blob/master/doc/connectivity-semantics-and-api.md
that should answer your questions.
gRPC tries to manage connections for you, so you can assume the channel
will become ready when you perform an RPC.
On
I should have pointed out that when queried the state I was using
.getState(true);
Parameters:
requestConnection - if true, the channel will try to make a connection if
it is currently IDLE
On Saturday, March 3, 2018 at 1:33:30 PM UTC-5, cr2...@gmail.com wrote:
>
> Hi -
> As a client is
Thanks .. So when I bring down the remote server Current state goes from
READY to IDLE . the channel stays in shutdown terminated both to false.
It seems to stay that way. At what point would it ever transition out of
READY? I tried bringing the remote endpoint back up and that instance