Thanks. Do you guys also do most of your retries on the client-side? For example, for optimistic locking exceptions, we return ABORTED status. In general, do you think it's better to automatically retry those failures on client-side?
On Wednesday, August 3, 2016 at 9:17:13 PM UTC-4, Josh Humphries wrote: > > A custom method option in the proto file is the way we're doing this at > Square. We also use other custom method options to influence other kinds of > retry policies not implemented in that pull request: latency-triggered > retries, where another attempt is made before the first call completes if > it's taking too long. > -- 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 post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/grpc-io/2ffab03b-fad5-49e4-b099-9865356ba6a9%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
