You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tapestry.apache.org by "Jochen Kemnade (JIRA)" <ji...@apache.org> on 2015/07/16 09:52:05 UTC
[jira] [Closed] (TAP5-466) Support parallel processing behavior via
a ParallelDecorator service
[ https://issues.apache.org/jira/browse/TAP5-466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jochen Kemnade closed TAP5-466.
-------------------------------
Resolution: Invalid
We assume this is no longer relevant and therefore close it.
If you still have this issue in a recent Tapestry version (such as 5.3.8 or the latest 5.4 preview release), feel free to provide the necessary information and reopen.
> 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)