After some studies on Strut's internals, Servlet 3's spec, other framework's internals and a few blog posts, I think I'm good to go for SLS case (Short request processing, Long action execution, Short response processing) :)
I putted this on monitor at [1]. [1] https://issues.apache.org/jira/browse/WW-4874 On 10/9/2017 12:56 PM, Christoph Nenning wrote: > I'd rather have just a very thin wrapper around servlet api, like so: > - actions might be declared async, this causes struts to call > request.startAsync() > - applications using that must use their own threads to do work (as with > servlet api) > - it should still be possible to use all struts results > - we need some mechanism for the action to trigger result execution and > cleanup of async context (result may run in application managed thread as > well) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
