[ https://issues.apache.org/jira/browse/TAP5-466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jochen Kemnade updated TAP5-466: -------------------------------- Labels: bulk-close-candidate (was: tapestry5-review-for-closing) This issue has been last updated more than a year ago, has no assignee, affects an old version of Tapestry that is not actively developed anymore, and is therefore prone to be bulk-closed in the near future. If the issue still persists with the most recent development preview of Tapestry (5.4-beta-26, available from Maven Central), please update it as soon as possible. In the case of a feature request, please discuss it with the Tapestry developer community on the d...@tapestry.apache.org mailing list first. > Support parallel processing behavior via a ParallelDecorator service > -------------------------------------------------------------------- > > Key: TAP5-466 > URL: https://issues.apache.org/jira/browse/TAP5-466 > Project: Tapestry 5 > Issue Type: Improvement > Components: tapestry-ioc > Affects Versions: 5.1.0.0 > Reporter: Howard M. Lewis Ship > Priority: Minor > Labels: bulk-close-candidate > > The concept here is similar to the proposed LazyDecorator, except that the > method invocation will be evaluated, in parallel, in a worker thread. This > implies that there's a service for managing worker threads as well. > Again, this only applies to methods that return an interface type (that can > encapsulate the future value) and throw no checked exceptions. > The returned object would delegate to a Future object linked to excecution of > the method invocation in a worker thread. -- This message was sent by Atlassian JIRA (v6.3.4#6332)