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

Posted to dev@syncope.apache.org by "ASF subversion and git services (Jira)" <ji...@apache.org> on 2022/12/24 14:23:00 UTC

[jira] [Commented] (SYNCOPE-1716) Concurrent handling for pull and push tasks

    [ https://issues.apache.org/jira/browse/SYNCOPE-1716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17651793#comment-17651793 ] 

ASF subversion and git services commented on SYNCOPE-1716:
----------------------------------------------------------

Commit 2ccbf857a8009c41fd8344b98f002282e1bb8b6e in syncope's branch refs/heads/master from Francesco Chicchiriccò
[ https://gitbox.apache.org/repos/asf?p=syncope.git;h=2ccbf857a8 ]

[SYNCOPE-1716] Introducing PushTask's and PullTask's ThreadPoolSettings (#397)



> Concurrent handling for pull and push tasks
> -------------------------------------------
>
>                 Key: SYNCOPE-1716
>                 URL: https://issues.apache.org/jira/browse/SYNCOPE-1716
>             Project: Syncope
>          Issue Type: Improvement
>          Components: console, core, documentation
>            Reporter: Francesco Chicchiriccò
>            Assignee: Francesco Chicchiriccò
>            Priority: Major
>             Fix For: 3.0.1
>
>
> ConnId's implementations for {{SyncApiOp}} and {{SearchApiOp}} (used by Syncope to pull in all [supported modes|https://syncope.apache.org/docs/3.0/reference-guide.html#pull-mode]) are designed to invoke sequentially the provided {{handler}} on each matching item.
> At present, Syncope pull handler is sequentially processing each provided item.
> This is not mandatory, however: pull handler's logic can be changed to optionally support concurrent processing, while keeping sequential acceptance.
> Similar logic applies to push tasks.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)