[
https://issues.apache.org/jira/browse/FELIX-1913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12794044#action_12794044
]
Carsten Ziegeler commented on FELIX-1913:
-----------------------------------------
Yes, the order is preserverd - however if an event handler takes longer than
the timeout, this handler still runs when the next event from the stack is
processed.
I've run it through my tests and they look fine (which is obvious as the whole
point of this change is to make my tests look good), so I'm looking forward to
your additional tests.
By this, I assume the TCK runs fine on the implementation, right?
> 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, ea2.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.
