On 25/07/2025 07:07, Paulo Miguel Almeida wrote:
<snip/>
Question for the tomcat maintainers
-----------------------------------
Is that something that you would be interested in getting merged into
Tomcat's source code? I'm happy to make changes to the approach of
course... just wanna know if there is any appetite for it
Personally I am neutral on this proposal at this point.
I do have some questions / comments:
1. Why not use threadPriority on each of the connectors? I assume
because that doesn't allow a single thread pool to be shared across
multiple connectors.
2. Why not use HTTP/2 + RFC 9218? I assume because that operates within
a single connection and you don't want to put all the reverse proxy
traffic in a single HTTP/2 connection.
3. What other approaches did you consider, reject and why?
4. How do you define priority for each connector element?
5. I'd be concerned that some folks may try to do too much with this.
Simple is good (c.f HTTP/2 prioritization from RFC 7540 with the HTTP/2
PRIORITY frame). If implemented, the documentation would need to be
clear that this was intended as a (very) coarse-grained solution.
6. It requires a new connection for each request from the reverse proxy
(i.e. disabled keep-alive). That should be fine.
7. How much care needs to be taken in the reverse proxy to ensure pages
aren't part high priority resources and part low priority. Instinctively
that seems like it would be problematic. Is it?
8. Just wondering (haven't thought it through) if you could implement
something with the Servlet Async API. Something like a filter that put
every request into async mode and then dispatched to the original URI in
priority order.
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
