ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dmitriy Govorukhin <dmitriy.govoruk...@gmail.com>
Subject Re: async operation is not fair async
Date Fri, 11 May 2018 17:38:48 GMT
Dmitriy S,

Why method named as "async" but does not work as async? This is misleading.

getAllAsync() is a special case. Not always you can use getAllAsync() instead
of multiple getAsync().
In this topic, I wanna discuss problem not only for the GET operation but
also all async operation behavior in the one thread.

In compute grid we can run multiple async compute operation in the one
thread, so why we can not do this for cache?

On Fri, May 11, 2018 at 8:33 PM, Dmitriy Setrakyan <dsetrakyan@apache.org>

> On Fri, May 11, 2018 at 6:29 PM, Dmitry Pavlov <dpavlov.spb@gmail.com>
> wrote:
> > IMO you can complete async operations one before another if these
> > operations are related to independent data.
> >
> > It is strange why Ignite users are not confused by current API. So I
> > support Dmitriy's G. suggestion.
> >
> Again, this is a solution looking for a problem. Nobody complains about
> this, so there really isn't any issue. There are so many other tasks we
> could focus on. Let's not fix what's not broken.
> D.

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message