Promises and executors

[Raymond Auge <ra...@liferay.com>]

Aries async has a PromiseImpl which allows an executor as argument.

Should it also implement a Deferred which can do the same?

And finally, should this DeferredImpl also provide the functions of the
static Promises class, but using the configured executor

I guess my main concern is that using Promises.all has no way to appoint an
executor for it's own promise which is created from a Deferred.

-- 
*Raymond Augé* <http://www.liferay.com/web/raymond.auge/profile>
 (@rotty3000)
Senior Software Architect *Liferay, Inc.* <http://www.liferay.com>
 (@Liferay)
Board Member & EEG Co-Chair, OSGi Alliance <http://osgi.org> (@OSGiAlliance)

Re: Promises and executors

[Timothy Ward <ti...@apache.org>]

Hi Ray,

The Deferred is a public type defined by the OSGi specification - it would be a very bad thing for Aries to add new public API to it, and it would mean that Aries Promises would fail the OSGi CT. If you do want a new method on Deferred that requires a change to the specification. Otherwise if you want the Aries behaviour then the correct way to do this is to use the Aries PromiseImpl (which is an exported API type).

Regards,

Tim


> On 11 Aug 2017, at 16:51, Raymond Auge <ra...@liferay.com> wrote:
> 
> Aries async has a PromiseImpl which allows an executor as argument.
> 
> Should it also implement a Deferred which can do the same?
> 
> And finally, should this DeferredImpl also provide the functions of the
> static Promises class, but using the configured executor
> 
> I guess my main concern is that using Promises.all has no way to appoint an
> executor for it's own promise which is created from a Deferred.
> 
> -- 
> *Raymond Augé* <http://www.liferay.com/web/raymond.auge/profile>
> (@rotty3000)
> Senior Software Architect *Liferay, Inc.* <http://www.liferay.com>
> (@Liferay)
> Board Member & EEG Co-Chair, OSGi Alliance <http://osgi.org> (@OSGiAlliance)