Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Distribution Providers
Introduction
The Remote Services/Remote Service Admin specifications (chaps 100 and 122 in OSGi Enterprise spec) allows for the use of distinct distribution providers for every exported remote service. Distribution providers are responsible for the actual marshalling/serialization and network communication that takes place when a consumer invokes a method on a remote service.
The ECF Architecture allows the use of multiple distribution providers. Further, ECF's open APIs and implementations allows the creation of new distribution providers that may be based upon existing providers or may be created from scratch using any desired transport protocols and/or serialization formats.
Remote Services API
ECF has an API for distribution providers called the Remote Services API. An implementation of this API is the only thing required of distribution provider implementations for them to be successfully used as a standards/compliant implementation of RS/RSA.
Symbolic Name: org.eclipse.ecf.remoteservice
Dependencies: EE: J2SE-1.5+', Framework: OSGi R5+, ECF Core, org.eclipse.equinox.concurrent.future bundle
Javadoc
All RSA distribution providers must implement the Remote Services API.
Existing Open Source Providers
ECF Generic Distribution Provider