You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tapestry.apache.org by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org> on 2009/01/24 19:23:59 UTC
[jira] Created: (TAP5-466) Support parallel processing behavior via
a ParallelDecorator service
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
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 is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (TAP5-466) Support parallel processing behavior
via a ParallelDecorator service
Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12666969#action_12666969 ]
Howard M. Lewis Ship commented on TAP5-466:
-------------------------------------------
Of course, the question is do you actually gain performance this way? I think there are scenarios where you might, such as I/O bound operations that include loading pages and templates and component message catalogs.
> 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
>
> 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 is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (TAP5-466) Support parallel processing behavior
via a ParallelDecorator service
Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12666971#action_12666971 ]
Howard M. Lewis Ship commented on TAP5-466:
-------------------------------------------
See notes in TAP5-463 about the viability/safety of this concept.
> 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
>
> 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 is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (TAP5-466) Support parallel processing behavior
via a ParallelDecorator service
Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12666969#action_12666969 ]
Howard M. Lewis Ship commented on TAP5-466:
-------------------------------------------
Of course, the question is do you actually gain performance this way? I think there are scenarios where you might, such as I/O bound operations that include loading pages and templates and component message catalogs.
> 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
>
> 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 is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (TAP5-466) Support parallel processing behavior
via a ParallelDecorator service
Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12666971#action_12666971 ]
Howard M. Lewis Ship commented on TAP5-466:
-------------------------------------------
See notes in TAP5-463 about the viability/safety of this concept.
> 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
>
> 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 is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.