On 06/12/2022 18:19, Konstantin Kolinko wrote:
вт, 6 дек. 2022 г. в 19:21, Mark Thomas <ma...@apache.org>:
Hi all,
I plan to implement RFC 9218 [1] for HTTP/2 in Tomcat 11. Depending on
how that goes, I may back-port the changes.
Given the difficulties we have in prioritizing creation of responses, I
plan to continue the current approach of prioritizing the sending of
data when the connection window size is smaller than the currently
active streams have collectively requested.
My rough plan at this stage, which is likely to change as I work through
the implementation, is:
- remove all the code that supports the current priority tree approach
- include SETTINGS_NO_RFC7540_PRIORITIES in the initial settings
- implement the new priority scheme - expected to be a much simpler
algorithm in Http2UpgradeHandler.allocate()
Mark
[1] https://www.rfc-editor.org/rfc/rfc9218.html#name-priority-parameters
+1
Sounds reasonable.
I added a link to [1] to our Specifications page on the wiki,
https://cwiki.apache.org/confluence/display/TOMCAT/Specifications
Tx.
It appears I have hit a distraction.
RFC 9218 (HTTP priorities) defines the Priority header in terms of RFC
8941 (structured fields).
From what I have seen on the IETF HTTP WG mailing list and from the
HTTP workshop I attended in November, HTTP is moving towards using
structured fields for everything. I think a generic structured field
parser is something worth having. I'm going to work on that first and
then come back to HTTP priorities.
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
