For unary RPC method calls, passing a context to the RPC method call is an Ok way to ensure that WaitForReady() doesn't hang forever. This is however tricky for streaming RPC method call, since setting the context also determines how long the entire stream will live for.
Is there a way to implement an upper limit on how long WaitForRead() waits for the channel to reach the READY state? I think a dedicated goroutine to monitor the state of the channel may work such that it is invoked every time we have a RPC method call..? Thanks, Amit. -- You received this message because you are subscribed to the Google Groups "grpc.io" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/grpc-io/CANODV3%3DfkRP707O63_0Ug50X1gz3o4Z%2B7hC3PA8pcAyBWRhUpQ%40mail.gmail.com.
