Dear Gul: One of the major pros of OSGi framework is, that she suggest us use White Board pattern to eliminate the drawbacks of the traditional "Listener" pattern.
One of the services provided by the framework, called "Event Admin Service" may be a good example for you. It supports not only sync message delivery, but async delivery as well. Please refer to the specification of Event Admin Service [Service Compendium 113, OSGi Spec 4.1] for more information. Enjoy! BR Difu On Thu, Oct 23, 2008 at 5:22 PM, Gul Onural <[EMAIL PROTECTED]> wrote: > > > Our current product architecture heavily relies on asynchronous > communication (through the listeners) between the components. > > In the OSGI R4 spec, I can see how synchronous communication between the > services are done, but I don't see anything about the > > asynchronous communication. > > What is the design pattern people used to implement asynchronous (event > driven) communication between the osgi services ? > > Gul > > _______________________________________________ > 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
