A major difference is that, if retries are enabled, the server can reply with an error code that's been configured as retryable and the client can retry the RPC.
On Thu, Dec 26, 2019 at 2:07 AM Elhanan Maayan <[email protected]> wrote: > > from my POV those seem to be identical except for the fact that > waitForReady doesn't execute calls until channel is read while enableRetry > does, why should that matter? (if i'm using steaming rpc) > > -- > 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/2ea04be3-a7c9-44c0-9539-00ae7394a6f8%40googlegroups.com > <https://groups.google.com/d/msgid/grpc-io/2ea04be3-a7c9-44c0-9539-00ae7394a6f8%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- 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/CALUXJ7gQet3q1jqfmv7aEVAC4O_OhGUEHQn6jyRkZ1RtHTsyeQ%40mail.gmail.com.
