|Limit the scope - definitions [message #6588]
||Thu, 13 October 2005 19:46
| No real name
Registered: July 2009
Since the Eclipse Rich Client Platform is an implementation (albeit|
currently incomplete) of the OSGi Service Platform specification, it might
be useful to review what that spec says:
"Service Platform - A instantiation of a Java VM, an OSGi Framework, and
a set of running bundles."
In Eclipse, bundles are known as plug-ins and the OSGi Framework is
implemented in the Core/Runtime. Also, in OSGi the word "service" has a
precise meaning reflecting the mechanism by which one bundle can make a
service object available to other bundles (think Eclipse extensions and
Description of the OSGi Framework from the OSGi Service Platform
"The Framework forms the core of the OSGi Service Platform specifications.
It provides a general-purpose, secure, and managed Java framework that
supports the deployment of extensible and downloadable service applications
known as bundles."
In summary, it seems that, within the Eclipse/OSGi environment, a framework
establishes the rules of engagement for an application while a platform is
deployable, enforces the framework specification and is capable of hosting
compliant applications together with other tools, services and related
applications that support fulfillment of the platform purpose.
I'll let this go now, but this distinction between a framework and platform
will help me explain why I think a limitation in scope is desirable. To
continue that part of the discussion, I'll comment in a response to Ken's
Powered by FUDForum
. Page generated in 0.01586 seconds