[news.eclipse.technology.ecp] Re: Demo application and source code from

[Peter.Kriens@xxxxxxxxx (Peter Kriens)]

Though a service has some overhead in an OSGi Framework, we have always 
tried to keep it minimal. During R4 we went through a lot of hard work to 
make it possible to register services lazily.

It has always been the intention to use the service registry for objects 
like your beans. We found that this had several advantages:

1. Simplicity
   a. Life cycle dynamicity is hard, services make it easy
   b. Same registry code for all internal registries
   c. Single service model
   d. Single event model
   e. Security (if needed)
2. Efficiency
   a. OSGi Service registries are highly optimized
   b. Lazy initialization
3. Power
   a. Filters
   b. Transparent because all relevant objects are visible
   c. Blackboard (or as we call it whiteboard) model
   d. Proxying

In several instances, we found out that "private" registries were less 
efficient (and often deficient) in comparison to the OSGi service registry


Hope this helps,
 Peter Kriens