>
> Yes. An application (handler's implementations) may depend on that.


 Aside from that filter bug Ethan mentioned, have you seen such cases? I
usually see people take it as a given that the default impl can serve
multiple requests and have to tell them to use an executor. If we decide
against changing the executor, perhaps we should update the Javadoc to
better clarify that the default serves requests serially.


> Using a VirtualThreadPerTaskExecutor would eliminate most of
> these questions, but virtual threads were not there when
> the API was designed


True enough, but they're here now, so it's a golden opportunity.

Reply via email to