[
https://issues.apache.org/jira/browse/FELIX-1913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12785833#action_12785833
]
Sven Ludwig commented on FELIX-1913:
------------------------------------
Hello, I find this an interesting thread and want to contribute with a
question. First, what I have understood is that for one event-sending thread
the events will be processed in serial. However, if two events are sent by two
different threads, the events are processed concurrently.
I am wondering why the assumption that events sent by different threads may be
processed concurrently. This is just a question out of interest, and maybe it
helps to clarify the situation even more. I am considering a situation in which
the event sender (wherever the events come from) may be concurrent
implementations and thus the same end-point-sender may not send its events via
the same thread - maybe such a situation exists and thus may be a problem here
for the patch.
> 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.
