<div dir="ltr"><div dir="ltr"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Yes. An application (handler's implementations) may depend on that.</blockquote><div><br></div><div> 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.</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Using a VirtualThreadPerTaskExecutor would eliminate most of<br>these questions, but virtual threads were not there when<br>the API was designed</blockquote><div><br></div><div>True enough, but they're here now, so it's a golden opportunity.</div></div>
<input name="virtru-metadata" type="hidden" value="{"email-policy":{"disableCopyPaste":false,"disablePrint":false,"disableForwarding":false,"enableNoauth":false,"expandedWatermarking":false,"expires":false,"sms":false,"expirationNum":1,"expirationUnit":"days","isManaged":false,"persistentProtection":false},"attachments":{},"compose-id":"2","compose-window":{"secure":false}}"></div>