Retry middleware implements retry based on timeout.
But when timeout happens prev request can still be in fly and consume resources. I.e. prev request is not stopped/canceled.
Browsers limit number of concurrent requests. And default timeout for fetch varies in different browsers and can be 2-3 minutes.
Since we are not going to wait for prev request to be finished should we cancel/stop it?
gtkatakura
commented
3 years ago
Retry middleware implements retry based on timeout. But when timeout happens prev request can still be in fly and consume resources. I.e. prev request is not stopped/canceled. Browsers limit number of concurrent requests. And default timeout for
fetchvaries in different browsers and can be 2-3 minutes.Since we are not going to wait for prev request to be finished should we cancel/stop it?