> You cannot use thread-local reliably starting in Jakarta Servlet 5.
Our undersatanding has been that a given request is still thread-locked from start to finish even though there are changes to the model in how requests are dispatched, as long as one didn't call out to some kind of asynchronous API or something that could suspend the processing of the request. We have looked into the issue and couldn't find any statements that a given servlet request is allowed to switch threads mid-request or how that could possibly make any sense. How would the container even get a chance to do so? But to be fair, I have expressed concerns about it and we have been aware that there are changes supposedly coming aorund that. Every time we look, we can't find the clarity we need about what it actually means in practice. And if it breaks, we'll be stuck because I don't think we have any other practical options. If you have some kind of information somewhere you could point us to about what it actually means that a thread can be swapped out or how/when that could possibly happen, it would be useful. -- Scott _______________________________________________ jetty-users mailing list jetty-users@eclipse.org To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jetty-users
