J
John Smith
ORIGINALLY POSTED TO microsoft.public.dotnet.framework.compactframework
NEWSGROUP
my letter is about industrial application of .NET Framework and .NET CF.
Particularly, I want to talk about creating something like the OSGi
Framework (www.osgi.org, based on Java) for .NET platform. Are there any
developers/sw-architects who would like to join me? My current focus is a
life cycle management module. I need to install assemblies dynamically to
Global Assemblies Cache (GAC), execute their Start method (if exists) and on
demand stop them (execute Stop method before) and uninstall.
The project is going to be open source. I'm thinking about opening a
SourceForge account and CVS. So, please, let me know if you are interested
or have any questions/ideas, here or by email.
Brief description of OSGi Framework follows...
---8<---
The OSGi service platform delivers an open, common architecture for service
providers, developers, software vendors, gateway operators and equipment
vendors to develop, deploy and manage services in a coordinated fashion. It
enables an entirely new category of smart devices due to its flexible and
managed deployment of services. The primary targets for the OSGi service
platform are devices such as set top boxes, service gateways, cable modems,
consumer electronics, PCs, industrial computers, cars, smart handhelds and
more. These devices that implement the OSGi specifications will enable
service providers like telcos, cable operators, utilities, and others to
deliver differentiated and valuable services over their networks.
The OSGi framework and specification facilitates the installation and
operation of multiple services on a single services platform device (again.
examples being, set-top box, cable or DSL modem, PC, Web phone, automotive,
multimedia platform device or dedicated residential gateway). The
specifications delineate Application Programming Interface (API) standards
for a platform execution environment. Services platforms must support these
APIs in order to conform to the OSGi specification. The APIs address service
cradle-to-grave life cycle management, inter-service dependencies, data
management, device management, client access, resource management and
security. Using these APIs, end-users can load network-based services on
command from the service provider while the platform manages the
installation, versioning and configuration of these services.
The OSGi Alliance is committed to evolving its specifications to meet
emerging market needs. Based on identified requirements, OSGi Expert
Groups -- which address architecture, core platform, and vehicle services --
develop extensions, new service APIs, and new features to simplify
programming, and enhance user administration and configuration management.
OSGi specifications are publicly available. Additionally, the OSGi Alliance
fosters development tools and resources through its website and other means
and enables service providers and device manufacturers to leverage content
and services from a multitude of developers and content developers.
I started my research on this subject almost 1 year ago. It looks like .NET
have virtually everything what OSGi uses from Java, even some things (e.g.
assemblies) are there out of the box, so you don't need to reinvent them.
Release 1 (May 2000)
-----------------------
.. Framework
.. Log Service
.. Http Service
.. Device Access
New in release 2 (October 2001)
----------------------------------
.. Package Administration service
.. Permission Administration service
.. Configuration Administration service
.. Preferences service
.. User Administration service
.. Metatyping
.. Service Tracker utility (a version for Framework 1.0 is created as well)
New in release 3 (March 2003)
--------------------------------
.. Wire Admin service
.. Measurement utility
.. Start Level service
.. Execution Environments
.. URL Stream and Content Handling
.. Dynamic Import
.. Position utility
.. IO service
.. XML service
.. Jini service
.. UPnP service
.. OSGi Name-space
.. Initial Provisioning service
---8<---
With best regards,
sect
sect0r527[At>gmx[Dot>net
NEWSGROUP
my letter is about industrial application of .NET Framework and .NET CF.
Particularly, I want to talk about creating something like the OSGi
Framework (www.osgi.org, based on Java) for .NET platform. Are there any
developers/sw-architects who would like to join me? My current focus is a
life cycle management module. I need to install assemblies dynamically to
Global Assemblies Cache (GAC), execute their Start method (if exists) and on
demand stop them (execute Stop method before) and uninstall.
The project is going to be open source. I'm thinking about opening a
SourceForge account and CVS. So, please, let me know if you are interested
or have any questions/ideas, here or by email.
Brief description of OSGi Framework follows...
---8<---
The OSGi service platform delivers an open, common architecture for service
providers, developers, software vendors, gateway operators and equipment
vendors to develop, deploy and manage services in a coordinated fashion. It
enables an entirely new category of smart devices due to its flexible and
managed deployment of services. The primary targets for the OSGi service
platform are devices such as set top boxes, service gateways, cable modems,
consumer electronics, PCs, industrial computers, cars, smart handhelds and
more. These devices that implement the OSGi specifications will enable
service providers like telcos, cable operators, utilities, and others to
deliver differentiated and valuable services over their networks.
The OSGi framework and specification facilitates the installation and
operation of multiple services on a single services platform device (again.
examples being, set-top box, cable or DSL modem, PC, Web phone, automotive,
multimedia platform device or dedicated residential gateway). The
specifications delineate Application Programming Interface (API) standards
for a platform execution environment. Services platforms must support these
APIs in order to conform to the OSGi specification. The APIs address service
cradle-to-grave life cycle management, inter-service dependencies, data
management, device management, client access, resource management and
security. Using these APIs, end-users can load network-based services on
command from the service provider while the platform manages the
installation, versioning and configuration of these services.
The OSGi Alliance is committed to evolving its specifications to meet
emerging market needs. Based on identified requirements, OSGi Expert
Groups -- which address architecture, core platform, and vehicle services --
develop extensions, new service APIs, and new features to simplify
programming, and enhance user administration and configuration management.
OSGi specifications are publicly available. Additionally, the OSGi Alliance
fosters development tools and resources through its website and other means
and enables service providers and device manufacturers to leverage content
and services from a multitude of developers and content developers.
I started my research on this subject almost 1 year ago. It looks like .NET
have virtually everything what OSGi uses from Java, even some things (e.g.
assemblies) are there out of the box, so you don't need to reinvent them.
Release 1 (May 2000)
-----------------------
.. Framework
.. Log Service
.. Http Service
.. Device Access
New in release 2 (October 2001)
----------------------------------
.. Package Administration service
.. Permission Administration service
.. Configuration Administration service
.. Preferences service
.. User Administration service
.. Metatyping
.. Service Tracker utility (a version for Framework 1.0 is created as well)
New in release 3 (March 2003)
--------------------------------
.. Wire Admin service
.. Measurement utility
.. Start Level service
.. Execution Environments
.. URL Stream and Content Handling
.. Dynamic Import
.. Position utility
.. IO service
.. XML service
.. Jini service
.. UPnP service
.. OSGi Name-space
.. Initial Provisioning service
---8<---
With best regards,
sect
sect0r527[At>gmx[Dot>net