Skip to main content
Jump to: navigation, search

Difference between revisions of "ECF/Asynchronous Remote Services"

< ECF
(Asynchronous Remote Services)
Line 14: Line 14:
 
</source>
 
</source>
  
Once a consumer of this service gets a valid service reference (i.e. through ServiceTracker, injection via declarative services (DS) or other injection framework, BundleContext.getServiceReference or others), it can actually invoke/use the service via a method call on 'hello':
+
Once a consumer of this service gets a valid service reference (i.e. through ServiceTracker, injection via declarative services (DS) or other injection framework, BundleContext.getServiceReference or others), it can actually invoke/use the service:
  
 
<source lang="java">
 
<source lang="java">
Line 98: Line 98:
 
</ol>
 
</ol>
  
====Another Example====
+
====Completable Future====
 +
 
 +
With Java8's introduction of the class <b>java.util.concurrent.CompletableFuture</b> and ECF 3.8.1 remote services, it's now possible to have a CompletableFuture rather than a future returned by the ECF remote services proxy creation
 
=====Original Service Interface=====
 
=====Original Service Interface=====
<source lang="java">package my.package;
+
<source lang="java">package org.eclipse.ecf.examples.remoteservices.hello;
  
public interface IFoo {
+
public interface IHello {
  
public String bar(URI uri, String something);
+
public String hello(String from);
 +
 
}
 
}
 
</source>
 
</source>
=====Asynchronous Service Interface=====
+
=====CompletableFuture Service Interface=====
 
<source lang="java">package my.package;
 
<source lang="java">package my.package;
import java.util.concurrent.Future;
+
import java.util.concurrent.CompletableFuture;
  
public interface IFooAsync {
+
public interface IHelloAsync {
  
     public Future<String> barAsync(URI uri, String something);
+
     public CompletableFuture<String> hello(String from);
 
}
 
}
 
</source>
 
</source>
 +
 +
This results in some very nice properties and runtime guarantees for remote service designers...the main one being that with CompletableFuture it's not necessary to call Future.get directly...but rather you can write nice, succinct and *guaranteed to be non-blocking and asynchronous* usage such as:
 +
 +
<source lang="java">
 +
 +
IHelloAsync helloAsync = ...get service via DS/injections, ServiceTracker or other
 +
 +
CompletableFuture<String> cf = helloAsync("slewis");
 +
 +
cf.thenAccept((response) -&gt; System.out.println("response to hello: " + response));
 +
 +
</source>
 +
 +
The above code, while being very succinct has absolutely no blocking calls, meaning that consumers can be sure that the I/O and/or network traffic implementing the remote call will not block.
  
 
==Notes==
 
==Notes==

Revision as of 17:12, 8 April 2014

ECF's Remote Services API, which is used to implement OSGi remote services and remote service admin specifications, has the ability for consumers/clients to use asynchronous/non-block remote method calls.

Normal/Synchronous OSGi (Remote) Services

When an OSGi service is actually invoked today, this is done by the caller calling a method on the service. For example, consider a simple 'hello' service:

package org.eclipse.ecf.examples.remoteservices.hello;
 
public interface IHello {
 
	public String hello(String from);
 
}

Once a consumer of this service gets a valid service reference (i.e. through ServiceTracker, injection via declarative services (DS) or other injection framework, BundleContext.getServiceReference or others), it can actually invoke/use the service:

String response = helloService.hello("slewis");

With OSGi remote services, this 'helloService' may actually be a proxy. If invoked as above a proxy will marshall the method arguments (i.e. 'slewis' String in this case), and communicate with the remote service host via some network (i.e. via some protocol). If there is a result of the call, then it will then be unmarshalled and returned to the caller thread. With synchronous invocation the thread that calls 'hello' will block until this entire process is complete.

Asynchronous Remote Services

ECF has added the ability to declare asynchronous access to a remote method, so that the consumer can ge guaranteed that calling the service will not block. So, for example, it's now possible to make a non-blocking call to the hello service like this

Future<String> future = helloAsyncService.helloAsync("slewis");

With an ECF created asynchronous proxy, the consumer thread that calls helloAsyncService.helloAsync is guaranteed not to block, and the returned Future can be used to access the value at some later point.

With ECF's asynchronous proxies, neither the consumer nor the host have to actually implement the asynchronous proxy behavior. The proxy is automatically constructed by the ECF remote services implementation when accessed by a consumer.

At this point, you might ask: But how is the asynchronous proxy defined? i.e. where does the helloAsyncService come from?

The answer to this is that it is defined in a new/second service interface...called the asynchronous service interface that is related to the IHello service interface:

public interface IHelloAsync {
 
	public Future<String> helloAsync(String from);
}

Notice that this asynchronous service interface declaration resembles the IHello service interface declaration, but differs from it in several specific ways:

  1. The name is IHelloAsync rather than IHello
  2. The method name is helloAsync rather than hello
  3. The return value is Future<String>

With ECF remote services, when a IHello proxy is created, the proxy will also implement the IHelloAsync interface. So, for example

IHello helloService = ...get service via DS/injections, ServiceTracker or otherServiceTracker, or other...
if (helloService instanceof IHelloAsync) {
   IHelloAsync helloServiceAsync = (IHelloAsync) helloService;
   // call it asynchronously
   Future<String> future = helloAsync("slewis");
   // do other things
   String result = future.get();
   // do something with result...
}

or

IHelloAsync helloAsyncService = ...get service via DS/injections, ServiceTracker or other
   // call it asynchronously
   Future<String> future = helloAsync("slewis");
   // do other things
   String result = future.get();
   // do something with result...

This gives the consumer maximum flexibility in determining how a given invocation will occur (i.e. synchronously or asynchronously. The caller can use the synchronous service proxy, or the asynchronous service proxy. Or both invocation methods may be used.

All that's required is for the service interface to declare an *Async service type class using these rules:

  1. Class name must be [service interface classname]Async
    • Example: IHello -> IHelloAsync
  2. For any methods that should be exposed to the consumer via the asynchronous proxy
    • Name the method [methodName]Async
      • Example: hello -> helloAsync
    • The return value should always be of type java.util.concurrent.Future with the actual return type via the Future generic type...e.g. Future<String>

Completable Future

With Java8's introduction of the class java.util.concurrent.CompletableFuture and ECF 3.8.1 remote services, it's now possible to have a CompletableFuture rather than a future returned by the ECF remote services proxy creation

Original Service Interface
package org.eclipse.ecf.examples.remoteservices.hello;
 
public interface IHello {
 
	public String hello(String from);
 
}
CompletableFuture Service Interface
package my.package;
import java.util.concurrent.CompletableFuture;
 
public interface IHelloAsync {
 
    public CompletableFuture<String> hello(String from);
}

This results in some very nice properties and runtime guarantees for remote service designers...the main one being that with CompletableFuture it's not necessary to call Future.get directly...but rather you can write nice, succinct and *guaranteed to be non-blocking and asynchronous* usage such as:

IHelloAsync helloAsync = ...get service via DS/injections, ServiceTracker or other
 
CompletableFuture<String> cf = helloAsync("slewis");
 
cf.thenAccept((response) -&gt; System.out.println("response to hello: " + response));

The above code, while being very succinct has absolutely no blocking calls, meaning that consumers can be sure that the I/O and/or network traffic implementing the remote call will not block.

Notes


Eclipse Communication Framework
API
API DocumentationJavadocProviders
Development
Development GuidelinesIntegrators Guide

Back to the top