[
https://issues.apache.org/jira/browse/SYNCOPE-1716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17795081#comment-17795081
]
ASF subversion and git services commented on SYNCOPE-1716:
----------------------------------------------------------
Commit 920f51d5ecfa5b358f9fca91218d5ab5d5e00bfc in syncope's branch
refs/heads/master from flyue
[ https://gitbox.apache.org/repos/asf?p=syncope.git;h=920f51d5ec ]
[SYNCOPE-1716] fixed membership hashmap multi-threaded problem with concurrent
pull (#571)
> 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)
