Async RFC 206 (from March 03) at:
https://github.com/osgi/design/tree/master/rfcs/rfc0206
>From section 5.4 we learn how to start an asynchronous
invocation that has a return value:
List asyncList = asyncService.mediate(listRef);
Promise<Boolean> promise =
asyncService.call(asyncList.contains("badEntry"));
and one that has no return value (void method):
mediator.clear();
Promise<Boolean> promise = asyncService.call();
The text explains that the actual asynchronous invocation
doesn't take place until calling Async.call(), ie:
asyncService.call(asyncList.contains("badEntry"));
^ send ^ prepare
async async
call call
asyncList.clear(); // prepare async call
asyncService.call(); // send async call
Why did you choose this design, and did not choose to
let a proxied method send its own async call?
Best regards
Mike
_______________________________________________
OSGi Developer Mail List
[email protected]
https://mail.osgi.org/mailman/listinfo/osgi-dev
