Re: [whatwg/fetch] New Proposal: Fetch retry (Issue #1838)

annevk left a comment (whatwg/fetch#1838)

Here's how I would simplify some of this:

* Throw for retry in combination with `mode: "no-cors"`.
* I would keep the new request headers out of v1. As Mark notes there's overlap with IETF activity and it also seems fairly high-level for a low-level API such as `fetch()`. I'm also not entirely comfortable sharing this additional information about the end user's network environment with the server.
* Delivering the final network error upon max-age frees us from any worries about timing attacks and allows us to end retrying early and preserve end user resources when it's due to a policy, battery, or other relevant concern. Because of this we should probably require max-age to always be set.
* I think we should have recommended default values for delay and delayFactor. If we don't and they end up significantly varying across implementations, web developers will feel required to always set them instead. Alternatively we could require them to be always be set in v1 and throw otherwise, that would also be reasonable.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/fetch/issues/1838#issuecomment-3068365052
You are receiving this because you are subscribed to this thread.

Message ID: <whatwg/fetch/issues/1838/3068365052@github.com>