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: <CAGt6o8kwdNHd_n6kA3W8CeM6Yao3n0r=0vutfmR42Z=+HKyCNw@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>
 <CA+0=VoW59Z5REDTqwtLM2fpg=uLLDkQVpBdq1hajfG6gRJdsXw@mail.gmail.com> <CAGt6o8kwdNHd_n6kA3W8CeM6Yao3n0r=0vutfmR42Z=+HKyCNw@mail.gmail.com>
From: Vladimir Ozerov <vozerov@gridgain.com>
Date: Thu, 22 Dec 2016 14:09:44 +0300
Message-ID: <CAGt6o8=LiNTv98f=CxbyYsT1aYwTdAjSSOATF2BzQCRzyKh5ow@mail.gmail.com>
Subject: Re: Make async API great again
To: dev@ignite.apache.org
Content-Type: multipart/alternative; boundary=f403045f8ac48ec40405443d4ee9
archived-at: Thu, 22 Dec 2016 11:09:57 -0000

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

And several more improvements to future API:
1) Remove startTime() and duration() methods:
https://issues.apache.org/jira/browse/IGNITE-4479
2) Fix broken cancellation semantics:
https://issues.apache.org/jira/browse/IGNITE-4480

On Thu, Dec 22, 2016 at 1:40 PM, Vladimir Ozerov <vozerov@gridgain.com>
wrote:

> Gents,
>
> I created tickets for all proposed improvements:
> 1) Nice async API: https://issues.apache.org/jira/browse/IGNITE-4475
> 2) Do not process IO messages synchronously for local node:
> https://issues.apache.org/jira/browse/IGNITE-4476
> 3) Better IgniteFuture API and callback semantics: https://issues.
> apache.org/jira/browse/IGNITE-4477
>
> Please review it and let me know if you have any comments.
>
> Vladimir.
>
> On Wed, Dec 21, 2016 at 4:32 AM, Dmitriy Setrakyan <dsetrakyan@apache.org>
> wrote:
>
>> 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?
>> > > > >
>> > > >
>> > >
>> >
>>
>
>

--f403045f8ac48ec40405443d4ee9--