[
https://issues.apache.org/jira/browse/FELIX-1913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12794000#action_12794000
]
Karl Pauls commented on FELIX-1913:
-----------------------------------
Well, as i did say, we have to make sure we maintain the order of events and it
did sound like you don't. Sure enough, your implementation doesn't pass the tck
(complains about out-of-order delivery :-). Can you try to get me a patch (then
i will have a look during the chrismas break)?
> All events are processed in a 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, org.apache.felix.eventadmin-1.0.1-SNAPSHOT.jar
>
>
> The current event admin implementation puts all events into a queue and
> processes this queue 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.
> In the async mode, event deliver might take a long time as these events are
> processed one after the other as well.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
