Unfortunately, we still can't provide any ETA on this. We will definitely get back to this at some point, but we've got other higher priority work that will be occupying our attention for the next few quarters, so the soonest we might be able to get back to this would be toward the end of the year.
FWIW, I am personally committed to getting this done at some point, because I've already sunk about a year's worth of time into it, and I don't want that to have been for nothing. :) On Tue, Feb 26, 2019 at 3:42 PM <[email protected]> wrote: > Hi, I just wanted to bump this up - any updates on shipping retry support > <https://github.com/grpc/grpc/pull/10684> for public use? Thanks. > > On Monday, March 13, 2017 at 1:41:39 PM UTC-7, Mark D. Roth wrote: >> >> After much discussion with the DNS and security folks, we've decided on a >> way to address the potential security issue of allowing an attacker to >> inject a service config with a large number of retries or hedged requests. >> We will do this by imposing an upper bound on the max number of retries or >> hedged requests that are configurable via the service config. That upper >> bound will be 5 by default, but applications will be able to explicitly >> override it if needed via a channel argument. >> >> This approach not only limits the damage that can be caused by a >> malicious attacker but also damage that can be caused by a simple typo. >> >> Noah, can you please add a section about this to the design doc? Thanks! >> >> On Fri, Feb 10, 2017 at 4:31 PM, ncteisen via grpc.io < >> [email protected]> wrote: >> >>> I've created a gRFC describing the design and implementation plan for >>> gRPC Retries. >>> >>> Take a look at the gRPC on Github >>> <https://github.com/grpc/proposal/pull/12>. >>> >>> -- >>> 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]. >>> Visit this group at https://groups.google.com/group/grpc-io. >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/grpc-io/30e29cbc-439c-46c4-b54f-6e97637a0735%40googlegroups.com >>> <https://groups.google.com/d/msgid/grpc-io/30e29cbc-439c-46c4-b54f-6e97637a0735%40googlegroups.com?utm_medium=email&utm_source=footer> >>> . >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> >> >> -- >> Mark D. Roth <[email protected]> >> Software Engineer >> Google, Inc. >> > -- > 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]. > Visit this group at https://groups.google.com/group/grpc-io. > To view this discussion on the web visit > https://groups.google.com/d/msgid/grpc-io/d4134c00-fea6-4e23-a136-5ae730c261e6%40googlegroups.com > <https://groups.google.com/d/msgid/grpc-io/d4134c00-fea6-4e23-a136-5ae730c261e6%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- Mark D. Roth <[email protected]> Software Engineer Google, Inc. -- 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]. Visit this group at https://groups.google.com/group/grpc-io. To view this discussion on the web visit https://groups.google.com/d/msgid/grpc-io/CAJgPXp5Q%2B-Bm4DsxYNMxKzO9kP4B6_hTAZ%2BQzuPM2dGvCGMzAA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
