2017-08-18 10:19 GMT+02:00 Christoph Nenning <christoph.nenn...@lex-com.net>: > I think of it like async servlets. Execution of action could be delegated > to some executor thread pool and execution of result (which requires tcp > connection / http response stream) must be done with some callback. > > It is up to application to decide if they use async actions and which of > their actions shall be async. So if they have usecases like Dave described > (e.g. reading data from multiple backends) that would be candidates for > async actions.
I see it the same way, as an action level mechanism to allow parallelise execution of the same action. Regards -- Łukasz + 48 606 323 122 http://www.lenart.org.pl/ --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
