[
https://issues.apache.org/jira/browse/FELIX-1913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12785843#action_12785843
]
Carsten Ziegeler commented on FELIX-1913:
-----------------------------------------
As Karl statet the current implementation is according to the spec - however,
it is very slow in delivering synchronous events as they are put in in a single
queue. Apart from performance, there is no problem with this - but in some
cases performance matters, at least a little bit. If you're using the event
admin for notifications, especially to give a user a feedback or something like
that, it matters if the event takes 2 minutes to be delivered or 100ms. - And
yes, these are realistic figures.
The spec allows to dispatch events coming from different threads in parallel.
So in your example, if the events come from different threads, there is no
particular order mandated from the spec and therefore can safely be processed
in parallel.
> 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.
