You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@syncope.apache.org by "Francesco Chicchiriccò (JIRA)" <ji...@apache.org> on 2012/10/17 13:30:03 UTC

[jira] [Updated] (SYNCOPE-141) Concurrent propagation

     [ https://issues.apache.org/jira/browse/SYNCOPE-141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Francesco Chicchiriccò updated SYNCOPE-141:
-------------------------------------------

    Description: 
Add the option to execute propagation ops concurrently.

Consider that we must continue to propagate towards primary resources sequentially, in respect of the specified priority.
Maybe propagation ops towards non-primary resources can be executed sequentially in respect of the priorities specified and concurrently in case of resources with the same priority.

  was:
Add the option to execute propagation ops in parallel. Consider that we must continue to propagate towards primary resources sequentially, in respect of the specified priority.
Maybe propagation ops towards non-primary resources can be executed sequentially in respect of the priorities specified and in parallel in case of resources with the same priority.

        Summary: Concurrent propagation  (was: Parallel propagation ops)
    
> Concurrent propagation
> ----------------------
>
>                 Key: SYNCOPE-141
>                 URL: https://issues.apache.org/jira/browse/SYNCOPE-141
>             Project: Syncope
>          Issue Type: Improvement
>            Reporter: Francesco Chicchiriccò
>             Fix For: 1.3.0
>
>
> Add the option to execute propagation ops concurrently.
> Consider that we must continue to propagate towards primary resources sequentially, in respect of the specified priority.
> Maybe propagation ops towards non-primary resources can be executed sequentially in respect of the priorities specified and concurrently in case of resources with the same priority.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira