ECF/Distributed OSGi Services
ECF's support for Distributed OSGi Services is a layered set of application programming interfaces (APIs). As discussed in this blog entry...Those Leaky Networks, API layering allows service programmers and service consumers to decide which mechanisms are appropriate for any given distributed service, and to use the appropriate mechanisms, without sacrificing the ability to switch among multiple implementations of the actual wire protocol (referred to as 'providers' in ECF).
Here is a diagram showing the relationship between the various layered APIs in ECF's support of distributed OSGi. APIs are shown in white and gray, implementation/providers are shown in blue.
With this layering, it's possible for a given remote service to use one or both API levels shown above (i.e. the ECF RFC119 level, as well as ECF discovery/remote services level) to expose and remotely access a given remote service. Both of these approaches can be used simultaneously if desired.
Here are two pages (with source) showing the use of RFC119 and ECF remote services to expose and access a 'hello' remote service
- RFC119 - Getting Started with ECF's RFC119 Implementation
- Remote Services API - Getting Started with Using the ECF Remote Services API
|Eclipse Communication Framework|
|API Documentation • Javadoc • Providers • ECF/Bot Framework|
|Servers • Shared Editing • Shared Code Plug-in|
|Development Guidelines • Integrators Guide|