Hi, With the growing use of the message driven paradigm, for instance in the IOT market, I am questioning the completeness of the EventAdmin spec * EventHandler has no way of acknowledging that the message has been processed successfully * No standardized properties for defining QOS such as message persistent type (volitive/persistence), durability of connections So in my mind, EventAdmin is not supporting enough of the basic use case for asynchronous communication. Some critical issues are missing.
What would be possible steps be ? > A. Update EventAdmin (a few enhancements would do it) > B. Providing JMS wrapper bundle that exposes easy to use JMS services (==> JMS > is not a viable concept on for instance Celix) > C. Providing AMQP wrapper bundle that exposes easy to use AMQP services (==> > EventAdmin could be a wrapper across JMS and AMQP) My 2 cents : +1 for 1 Any suggestions, experience ,feedback would be much appreciated Best Frank
_______________________________________________ OSGi Developer Mail List [email protected] https://mail.osgi.org/mailman/listinfo/osgi-dev
