[SUGGESTION] Callback for deciding retry timeout

Question

[SUGGESTION] Callback for deciding retry timeout

mfn opened this issue 7 years ago · comments

The current implementation implements a hard-coded algorithm with a default_retry_multiplier.

This may be to inflexible if someone may want to use other means, like 2^{retryCount - 1} or similar.

As such it would be great if this could be a callback too, similar to what the \GuzzleHttp\RetryMiddleware::__construct(delay) does.

Casey McLaughlin · Answer 1 · Mon Oct 09 2017 03:59:05 GMT+0800 (China Standard Time)

Yep, I plan on implementing this.

I didn't include it thus far, because my focus was on the Retry-After use-case. If you want to submit a PR and tests, feel free; otherwise I'll get it implemented as soon as I can.

Casey McLaughlin · Answer 2 · Wed Feb 14 2018 03:20:39 GMT+0800 (China Standard Time)

Hi @mfn ... As of today's release (version 2.1), default_retry_multiplier now accepts a callable, per your suggestion.

You can read about how to use it here: https://github.com/caseyamcl/guzzle_retry_middleware#setting-default-retry-delay

Best regards!