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

@noamr commented on this pull request.



> @@ -8481,6 +8615,75 @@ 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;
+};
+
+interface FetchLaterResult {
+  readonly attribute boolean sent;
+};
+
+partial interface mixin WindowOrWorkerGlobalScope {
+  [NewObject] FetchLaterResult fetchLater(RequestInfo input, optional DeferredRequestInit init = {});

- Re `keepalive`, as per current spec it would drop only requests that have already started, meaning requests started due to `backgroundedTimeout`. But yea, makes sense that fetchLater requests are always keepalive.
- Can also be `DELETE` or `PUT`, no? I don't see why we need to limit that because of "the goal of the original pending beacon proposal".

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

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