Re: [whatwg/fetch] Deferred fetching (PR #1647)

@fergald commented on this pull request.



> @@ -8449,6 +8597,60 @@ with a <var>promise</var>, <var>request</var>, <var>responseObject</var>, and an
 </div>
 
 
+<h3 id=fetch-later-method>FetchLater method</h3>
+
+<pre class=idl>
+
+dictionary DeferredRequestInit : RequestInit {
+  DOMHighResTimeStamp backgroundTimeout;
+};
+
+partial interface mixin WindowOrWorkerGlobalScope {
+  [NewObject] Promise&lt;Response> fetchLater(RequestInfo input, optional DeferredRequestInit init = {});

In reality flipping to true means that the browser intends to send this and there is no longer anything you can do to stop it. In a multiprocess implementation the bit should flip *before* sending starts, otherwise there is a race (you could cancel a request that has already started).

`sent` is actually a little misleading since sending may not have actually started or even be possible (e.g. we went offline at just the wrong moment). We could consider `pending` or `cancellable`.


-- 
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/fetch/pull/1647#discussion_r1223714849
You are receiving this because you are subscribed to this thread.

Message ID: <whatwg/fetch/pull/1647/review/1471015267@github.com>