Hi Neil,
Thank you for the response.
Concurrent delivery is something that i really need in my architecture.
BTW i think that
a pubslih/subscribe model as the Event Admin is without concurrent
delivery does really not
make sense.
At the moment i'm using the following implementations:
1) Equinox ( seems not support concurrent delivery )
2) ECF (distributed event admin based on jms provider - i'm testing )
I would like to make a try with felix implementation too.
At the moment i've solved the problem modifying equinox event admin
implementation
and it seems to work, at the moment i'm doing some test... if i will
succeed i'll have
no problem on contributing to community.
Do you know any commercial product offering EA with concurrent delivery??
Regards sponsor to open source projects it depends what you mean,
what i could say is that:
a) My company have no problem in contributing back to the community our
modification of the original
open source code.
b) In the case of "Equinox" in the case we're going to sponsor some
enhancement who we need
to contact?? From 2010 We're already "member" of Eclipse foundation, i
don't know if this could be
considered as a sponsor.. btw feel free to write me and i'll let you know.
Andrea
Il 11/02/2010 12:38, Neil Bartlett ha scritto:
Andrea,
Concurrent delivery is certainly an option for EventAdmin implementers
to support, but it is not mandated by the specification.
To put it bluntly, I think that the existing open source
implementations come nowhere near to offering the kind of powerful
features that EventAdmin *potentially* supports. For example QoS
guarantees relating to concurrent delivery, detection of stalled
handlers, etc.
It's possible that there are commercial EventAdmin offering these
features; alternatively your organisation may be interested in
sponsoring enhancements to the open source implementations.
Regards
Neil
On Thu, Feb 11, 2010 at 11:21 AM, Andrea Zoppello<[email protected]> wrote:
Hi all,
I'm developing an OSGi application where i plan to use a lot the osgi Event
Admin Service.
Actually i'm using the equinox implementation, and maybe i'm wrong but it
seems that in this
implementation the event are delivered to event handler sequentially.
I'm using the postEvent method on EventAdmin.
What happen is that each event delivery by the EventAdmin seems to work with
only one
event delivery at any time, this means that if an event is handled by an
EventHandler all other
events pushed are blocked until this one has finished the work on
handleEvent method.
Maybe i'm wrong but i expected the Event Admin to be able to deliver the
event in parallel
way. It's obvious that this will be a bottleneck for me.
My doubt is if this is the right expected beahviour of Event Admin, or is
particular detail
of Equinox implementation.
Andrea
_______________________________________________
OSGi Developer Mail List
[email protected]
https://mail.osgi.org/mailman/listinfo/osgi-dev
_______________________________________________
OSGi Developer Mail List
[email protected]
https://mail.osgi.org/mailman/listinfo/osgi-dev
_______________________________________________
OSGi Developer Mail List
[email protected]
https://mail.osgi.org/mailman/listinfo/osgi-dev
