Re: [ecf-dev] Remote service question

[Wim Jongman <wim.jongman@xxxxxxxxx>]

The client can put a property in the service registration and then pass the same property in the request. The server looks up the service with that specific property. Something like:

Client:

..

props.setproperty("knockknock", "client01");

context.registerservice(CallBackService, props)
requestService.request(request.newinstance().with("knockknock","client1"), payload);

Server:
filter.setproperty("knockknock", request.getProperty("knockknock"));

refs = context.getAllServiceReferences(CallBackService,class, filter);

On Wed, Oct 22, 2014 at 12:40 AM, Scott Lewis <slewis@xxxxxxxxxxxxx> wrote:

Hi Hallvard,

On 10/21/2014 2:11 PM, Hallvard Trætteberg wrote:

<stuff deleted>

Yes, this is good idea, particularly if you want something more like streaming, since you don't need to have the same number of calls in each direction.

In Akka you can ask for the sender. Is there anything similar in ECF, so you don't need to discover the (host of the) callback service?

In ECF generic and other providers generally yes...but just to be clear there is nothing in OSGi RS spec about it.   That makes things more complicated since we are talking about associating two OSGi Remote Services.

Scott


_______________________________________________
ecf-dev mailing list
ecf-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/ecf-dev