In section 5.3 of RFC 7540 (HTTP/2), steam priority is defined.
It is assigned by "client" in order to recommend how the endpoint should
allocate resources
while managing concurrent streams.
As discussed in the comments of
https://java.net/jira/browse/SERVLET_SPEC-138, the priority
information can be set in a priority frame, which is not a HTTP request.
If applications/frameworks want to use priority information, they would
need to keep the
priority "tree" information.
This seems to be quite low level, likely handled in transport/network layer.
Is there value in exposing this in the Servlet API for applications to use?
This seems more to be a HTTP client side API feature.
Is there any concrete interesting use cases that EG experts have in mind?
Shing Wai Chan