[concurrency-interest] We need to add blocking methods to CompletionStage!
martinrb at google.com
Wed Sep 21 17:44:46 EDT 2016
On Wed, Sep 21, 2016 at 2:38 PM, Pavel Rappo <pavel.rappo at gmail.com> wrote:
> On Wed, Sep 21, 2016 at 9:43 PM, Martin Buchholz <martinrb at google.com>
> > What is happening instead is API providers not using CompletionStage as
> > return values in public APIs because of the lack of convenient blocking,
> > instead returning CompletableFuture, which is a tragic software
> > failure.
> On Wed, Sep 21, 2016 at 10:25 PM, Benjamin Manes <ben.manes at gmail.com>
> > I've gradually come to terms using CF as part of an API and haven't
> > experienced a downside yet.
> I agree with Benjamin and would like to hear more about how it's a
> "tragic software engineering failure".
Obviously I was exaggerating, but the software engineering benefits of
separating the producer and consumer users into separate types seems big
(like the Builder pattern for immutable collections). Would you use
CompletionStage if it had the other methods consumers need?
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Concurrency-interest