1784496 - The necko consumers should use the HTTP/3 priority's incremental flag

Status: RESOLVED FIXED

(Core :: Networking: HTTP, task, P3)

Description

[Dragana Damjanovic [:dragana]]

We have the implementation of the incremental flag from rfc9218, but the necko consumers do not use it at the moment.

We will determine which consumers should set the flag and implement the changes.

Comment 1

[Valentin Gosu [:valentin] (he/him)]

https://datatracker.ietf.org/doc/html/rfc9218#name-incremental

If a client makes concurrent requests with the incremental parameter set to true, serving requests with the same urgency concurrently might be beneficial. Doing this distributes the connection bandwidth, meaning that responses take longer to complete. Incremental delivery is most useful where multiple partial responses might provide some value to clients ahead of a complete response being available.

Comment 3

[Andrew Creskey [:acreskey]]

Images with progressive rendering should be a good candidate for enabling this flag.

Comment 4

[Valentin Gosu [:valentin] (he/him)]

Attachment: Bug 1784496 - The necko consumers should use the priority's incremental flag r=#necko

This patch sets the incremental flag on document and image channels

Comment 5

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/0e349ba1d6ad
The necko consumers should use the priority's incremental flag r=necko-reviewers,kershaw

Comment 6

[Cosmin Sabou [:CosminS]]

https://hg.mozilla.org/mozilla-central/rev/0e349ba1d6ad