this would change existing behavior and may break application code
when there are dependencies between listeners and how/when
they receive events.
I'm also not sure if your proposed change is in line with the spec.
> -----Original Message-----
> From: Miroslav Smiljanic [mailto:firstname.lastname@example.org]
> Sent: Freitag, 12. Oktober 2012 13:57
> To: email@example.com
> Subject: ObservationDispatcher - dispatch queued events in separate
> Hi all,
> I was wondering what would be argument not to distribute queued events in
> "ObservationManager" in separate threads.
> I mean after reading queued action, use thread from pool to serve
> I saw the case where one of the listeners was taking to much time to finis his
> operation letting all other to wait.
> Can someone give me light here? Thanks.
> Best regards,