Mailing-List: contact dev-help@ignite.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ignite.apache.org
MIME-Version: 1.0
In-Reply-To: <CAGt6o8nwTP+NAabkBs=0vhszJc9cGabavWLhY9VXdMABc4V+eg@mail.gmail.com>
References: <CAGt6o8k_prXL301ooihB1efjgrAXSPHL0UnrNM34k_rAEPUR8w@mail.gmail.com>
 <CA+0=VoVrs_efBzs4no0D1dARUpZyxoB7QbK4vbdrGq6F3wcnaQ@mail.gmail.com>
 <CAK2_iMO7MxeJaQTorG7A64VcUGUny53NibYyM_jgfQeZWYqxbQ@mail.gmail.com>
 <CA+0=VoXmLwkq=GQKGuwgXbcxbx43iu8NMjqHTB4XZk9sWgk1-A@mail.gmail.com>
 <CA+eZwrHRaCm1+fYRaxQQUkEEzK7XsetrZ2NTEHyCv633jqPyQw@mail.gmail.com>
 <CA+0=VoXNeVN18CS0LXQ9=cdTaO-qQ_GMVMr7DD2Q9PZpRe03ug@mail.gmail.com>
 <CAGt6o8mAhmXyvL8KuxiaNjqRJdtGO6touq0cyKgyxEN=mcLZxw@mail.gmail.com>
 <CA+0=VoXnL_RVhV5T+oheKJ80JtPtOhoFGk-QDuTfMFP3RbFZ2g@mail.gmail.com> <CAGt6o8nwTP+NAabkBs=0vhszJc9cGabavWLhY9VXdMABc4V+eg@mail.gmail.com>
From: Dmitriy Setrakyan <dsetrakyan@apache.org>
Date: Tue, 20 Dec 2016 17:32:53 -0800
Message-ID: <CA+0=VoW59Z5REDTqwtLM2fpg=uLLDkQVpBdq1hajfG6gRJdsXw@mail.gmail.com>
Subject: Re: Make async API great again
To: dev@ignite.apache.org
Content-Type: multipart/alternative; boundary=001a113f41a81c1ce70544212424
archived-at: Wed, 21 Dec 2016 01:33:36 -0000

--001a113f41a81c1ce70544212424
Content-Type: text/plain; charset=UTF-8

Would be nice if someone would prototype a new cache API and post the
generated javadoc here. I think we all will benefit from reviewing it.

On Tue, Dec 20, 2016 at 12:17 PM, Vladimir Ozerov <vozerov@gridgain.com>
wrote:

> Async API rework is mechanical addition of ~100 methods through copy-paste.
> Should not take more than a day to implement and more than another day to
> rework tests.
>
> On Tue, Dec 20, 2016 at 10:00 PM, Dmitriy Setrakyan <dsetrakyan@apache.org
> >
> wrote:
>
> > How difficult is this change? Does not look like it can be done
> overnight.
> >
> > On Tue, Dec 20, 2016 at 10:46 AM, Vladimir Ozerov <vozerov@gridgain.com>
> > wrote:
> >
> > > We already discussed this several months ago in other thread.
> > >
> > > "Async" methods is the most simple and straight API possible. .NET
> world
> > > goes this way all over their frameworks and nobody died. Hazelcast also
> > > goes this way. Java goes this way (see CompletableFuture). This is
> common
> > > and well-known practice. The most impacted part of our API will be
> cache,
> > > +33 new methods. Though, I do not see how it can affect learning curve.
> > >
> > > Agree that we should deprecate AsyncSupport gradually and remove it no
> > > earlier than in Apache Ignite 3.0.
> > >
> > > On Tue, Dec 20, 2016 at 9:31 PM, Dmitriy Setrakyan <
> > dsetrakyan@apache.org>
> > > wrote:
> > >
> > > > On Tue, Dec 20, 2016 at 10:28 AM, Sergi Vladykin <
> > > sergi.vladykin@gmail.com
> > > > >
> > > > wrote:
> > > >
> > > > > +1 For removing withAsync. It is a broken design.
> > > > >
> > > >
> > > > Sergi, do you also want to add all the async methods to the main API
> or
> > > do
> > > > you have some other design in mind?
> > > >
> > >
> >
>

--001a113f41a81c1ce70544212424--