https://issues.apache.org/bugzilla/show_bug.cgi?id=57284
--- Comment #5 from ftud...@libero.it --- Yes, indeed Im trying to call from a different thread. My apologies for not having checked the spec and for having instead just assumed it should work; my reasoning is that it can be very useful to start async mode in filters (so, early in the request processing chain) rather than in the servlet. For example I'm working on several web framework integrations with Quasar (https://github.com/puniverse/quasar), a technology that enables dispatching execution to "fibers" (which can be much cheaper than threads). Being able to dispatch potentially expensive filter processing to fiber-based execution contexts would be a good thing (plus it would make async processing more transparent for the framework being integrated). I think supporting more than the servlet spec mandates is not a bad thing per se, but in case in this circumstance this is not sensible in your opinion, would it be possible at least to throw some exception pointing at the wrong usage? TIA -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
