[
https://issues.apache.org/jira/browse/FELIX-1913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12785285#action_12785285
]
Carsten Ziegeler commented on FELIX-1913:
-----------------------------------------
The patch I applied handles stacked events like this:
- event A comes in and should be delivered to handlers D1 and D2
- D1 is notified first but issues a new event B
- event B is delivered
- D2 gets event A
Now I think that this is the correct handling for sync event handling.
> All synchronous events are processed in one queue
> -------------------------------------------------
>
> Key: FELIX-1913
> URL: https://issues.apache.org/jira/browse/FELIX-1913
> Project: Felix
> Issue Type: Improvement
> Components: Event Admin
> Affects Versions: eventadmin 1.0.0
> Reporter: Carsten Ziegeler
> Assignee: Karl Pauls
> Priority: Minor
> Attachments: ea.patch
>
>
> The current event admin implementation puts all events into one single queue
> and processes this queue is in one thread. This creates a bottleneck when
> different threads send events as they have to wait for other threads to be
> processed first. Events from different threads can be processed in parallel.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
