Re: [cdi-dev] async: back to completion future?
How much end user feedback has there been on this? I have to be honest that it surprises
me to find this out now.
This to me stands out as an obvious usability problem. CompletableFuture is the obvious
top level end user API, not CompletionStage. Not going with CompletableFuture is very
likely to confuse most people. The last thing we need is more potential usability problems
in Java EE APIs.
On Mar 6, 2016, at 9:39 AM, Romain Manni-Bucau
<rmannibucau(a)gmail.com> wrote:
Hi guys,
as a user having a ComlpetionStage makes me loose some JDK utilities, can we move back to
CompletionFuture?
It would allow for instance:
// doesn't work with CompletionStage
CompletionFuture.allOf(event1.fireAsync(...), event2.fireAsync(...))
.then(...)
Romain Manni-Bucau
@rmannibucau | Blog | Github | LinkedIn | Tomitriber
_______________________________________________
cdi-dev mailing list
cdi-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/cdi-dev
Note that for all code provided on this list, the provider licenses the code under the
Apache License, Version 2 (http://www.apache.org/licenses/LICENSE-2.0.html). For all other
ideas provided on this list, the provider waives all patent and other intellectual
property rights inherent in such information.
Attachments:
- attachment.html (text/html — 2.5 KB)