- From: Noam Rosenthal <notifications@github.com>
- Date: Fri, 06 Oct 2023 09:57:54 -0700
- To: whatwg/fetch <fetch@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Friday, 6 October 2023 16:58:00 UTC
[copying from Matrix] The reason why I like `activateAfter`: The fetch could be activated after the deadline or before, but for different reasons. The timeout duration is like a preference. The UA would activate before the timeout in case of termination or some such, and after the activation timeout for throttling/batching. The word "timeout" is maybe confusing because it's the opposite of the abort signal's timeout So `activateAfter` means the same as `activationTimeout` but it's clearer that it's "a timeout after which activation should take place" rather than "A timeout after which activation expires" or something like that. /cc @smaug---- @mingyc @fergald -- Reply to this email directly or view it on GitHub: https://github.com/whatwg/fetch/issues/1715#issuecomment-1751110216 You are receiving this because you are subscribed to this thread. Message ID: <whatwg/fetch/issues/1715/1751110216@github.com>
Received on Friday, 6 October 2023 16:58:00 UTC