ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Nikolay Tikhonov <ntikho...@gridgain.com>
Subject Re: API for asynchronous execution.
Date Tue, 29 Mar 2016 13:40:29 GMT
This approach works for cases when callback will be invoked on local node
(cache future, local listener and etc), but how user set a thread pool when
callback executed on remote nodes (remote filter, entry processor and etc)?

On Tue, Mar 29, 2016 at 2:57 PM, Vladimir Ozerov <vozerov@gridgain.com>
wrote:

> We already had discussion about it several months ago. Normal practice is
> to allow user specify thread pool where he would like to execute the
> callback. This is how things work in JDK CompletableFutures and Hazelcast
> futures, and this is the most flexible approach.
>
> On Tue, Mar 29, 2016 at 2:23 PM, Nikolay Tikhonov <ntikhonov@gridgain.com>
> wrote:
>
> > Hello Igniters,
> >
> > Lately I'm working on a ticket
> > https://issues.apache.org/jira/browse/IGNITE-2004. As part of the ticket
> > need to add API which will provide an ability to execute operation
> > asynchronously. The ability might be useful not only for continuous query
> > filter but also for cache and discovery events, cache futures (listen and
> > chain), messages and etc. I see the following options :
> > * Marker interface: IgniteAsyncCallback
> > * Annotation: @IgniteAsyncCallback
> >
> > I prefer the latest approach. Any thoughts on this?
> >
>

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