Support for OSGI R7 Remote Services
In the R7 final draft specification (chapter 100) detail was added about the use of Remote Service Intents. RS Intents describe a distribution provider's abstract capabilities. By way of example, several new standard intents have been defined, including osgi.basic and osgi.async.
The osgi.basic intent requires that a distribution provider support a remote service-specific timeout, as well as serialization of remote service arguments and return values include DTOs (Data Type Objects), java primitives, maps, collections, lists, OSGI Version, etc.
The osgi.async intent requires that remote service method signatures using CompletableFuture, Future, and OSGI's Promise be supported directly by the distribution provider. This allows non-blocking asynchronous remote services to be easily declared in the service interface, and implemented by the distribution provider. Here is an example remote service declaration that demonstrates how the osgi.async intent can be used. In a forthcoming tutorial, I'll show how such a small service can be easily defined, implemented, and remoted using ECF Remote Services.
ECF's remote services impl has multiple distribution providers, and open APIs for creating custom or extension providers. Most of the existing ECF distribution providers already available have been updated to implement the R7-standardized intents. Others will be updated prior to and after Photon release.
In the R7 final draft specification (chapter 100) detail was added about the use of Remote Service Intents. RS Intents describe a distribution provider's abstract capabilities. By way of example, several new standard intents have been defined, including osgi.basic and osgi.async.
The osgi.basic intent requires that a distribution provider support a remote service-specific timeout, as well as serialization of remote service arguments and return values include DTOs (Data Type Objects), java primitives, maps, collections, lists, OSGI Version, etc.
The osgi.async intent requires that remote service method signatures using CompletableFuture, Future, and OSGI's Promise be supported directly by the distribution provider. This allows non-blocking asynchronous remote services to be easily declared in the service interface, and implemented by the distribution provider. Here is an example remote service declaration that demonstrates how the osgi.async intent can be used. In a forthcoming tutorial, I'll show how such a small service can be easily defined, implemented, and remoted using ECF Remote Services.
ECF's remote services impl has multiple distribution providers, and open APIs for creating custom or extension providers. Most of the existing ECF distribution providers already available have been updated to implement the R7-standardized intents. Others will be updated prior to and after Photon release.
No comments:
Post a Comment