Carlos O'Ryan

Results 588 comments of Carlos O'Ryan

Thanks for reaching out. Unfortunately I do not think we will be able to work on this during 2021-Q4.

Strike 2. We will want to do it, but no time yet.

## Background As described above, we have customers that need additional information to have finer grained control of their retry loops. They also wish to capture information from the retry...

Still on the roadmap. Maybe easier to implement via the per-call options.

I think the **problems** that this feature request wanted to solve are better addressed by the per-operation parameters in `storage::Client`. Applications can create any retry or backoff policy they want...

Just fixing the existing comment seems good enough.

We still want this, but I have made no progress. May be easier with the move to `rest-internal`.

This will be needed for the retry header work (2022-Q4)