Re: [quicwg/base-drafts] Break up H2 Frame Considerations (#2698)

[Martin Thomson <[e-mail]>]

martinthomson commented on this pull request.



> +PRIORITY frame on the request stream, if any, always comes first is explicitly
+stated.
+
+Exclusive prioritization has been removed, since implicitly reprioritizing other
+streams which might or might not exist yet is prone to race conditions even with
+the assumptions used to permit initial PRIORITY frames on request streams.
+
+HTTP/3 permits the prioritization of requests, pushes and placeholders that each
+exist in separate identifier spaces. The HTTP/3 PRIORITY frame replaces the
+stream dependency field with fields that can identify the element of interest
+and its dependency.
+
+### Header Compression Differences
+
+HPACK was designed with the assumption of in-order delivery. A sequence of
+encoded header blocks must arrive (and be decoded) at an endpoint in the same

The concept of header block fragments is an h2 thing.  h3 provides the entire header block in one go, more or less, right?

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/quicwg/base-drafts/pull/2698#discussion_r285444160