Catching up w/ my holiday mail...
On Dec 31, 2007, at 2:38 AM, Neil Bartlett wrote:
To use your example above, some bundle (BundleS) will register a
Skateboard
as a Vehicle to the system, which is tracked by BundleA. BundleA
will then
manage the Skateboard just like it would any other Vehicle. BundleS
should
not need to do anything regarding management other than registering
the
Skateboard as an OSGi service implementing Vehicle with a property
"id=skateboard". BundleA, from its perspective, just receives a
Vehicle that
it then takes control of as a Vehicle (it doesn't need to know any
of the
details of a Skateboard).
Is *exactly* how OSGi services work. BundleS would instantiate a
Skateboard in the normal way and register it under the Vehicle
interface. BundleA would then track services registered under the
Vehicle interface. BundleA only needs to know the Vehicle interface,
not any specific implementations of it.
I have a question. Do people really use OSGi services for such fine
grain objects such as vehicles? The California DMV comes to mind. I
was always under the impression that it was intended for more course
grained services.
Regards,
Alan
_______________________________________________
OSGi Developer Mail List
[email protected]
http://www2.osgi.org/mailman/listinfo/osgi-dev
