Re: [whatwg/fetch] Add support for compression dictionary transport (PR #1854)

@fred-wang commented on this pull request.



> @@ -8527,7 +8699,7 @@ dictionary RequestInit {
   any window; // can only be set to null
 };
 
-enum RequestDestination { "", "audio", "audioworklet", "document", "embed", "font", "frame", "iframe", "image", "json", "manifest", "object", "paintworklet", "report", "script", "sharedworker", "style", "text", "track", "video", "worker", "xslt" };
+enum RequestDestination { "", "audio", "audioworklet", "compression-dictionary", "document", "embed", "font", "frame", "iframe", "image", "json", "manifest", "object", "paintworklet", "report", "script", "sharedworker", "style", "text", "track", "video", "worker", "xslt" };

@pmeenan: By idle-level priority, are you referring to https://github.com/whatwg/html/pull/11620/changes#r3385960016 i.e. when the client decides to perform the fetch ? By "fetch priority" I was talking about https://web.dev/articles/fetch-priority?hl=en#effects which is destination-dependent and will affect how the server prioritizes requests (for example via [RFC9218](https://www.rfc-editor.org/rfc/rfc9218.html)). Since you are introducing a new destination, we need to decide how to handle it. I guess compression-dictionary destination would default to "VeryLow" / "Lowest" (using web.dev article's terminology). And we also need to decide a non-auto fetchpriority affects that default value, if that's desired.

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

Message ID: <whatwg/fetch/pull/1854/review/4674904189@github.com>