else.
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Async-messaging-tp8719p16157.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
ther
> things.
>
> Regards,
> Andrey
> _
> From: Daniel Stieglitz <dstiegl...@stainlesscode.com>
> Sent: Saturday, November 5, 2016 1:47 PM
> Subject: Async messaging
> To: <user@ignite.apache.org>
>
>
>
> Hi folks:
>
, November 5, 2016 1:47 PM
Subject: Async messaging
To: <user@ignite.apache.org<mailto:user@ignite.apache.org>>
Hi folks:
We are trying to get messaging working asynchronously. Take a look at the code
below:
IgniteMessaging rmtMsg = grid.message().withAsync();
def future = rmtMsg.s
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Async-messaging-tp8719p8733.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Look at the article about asynchronous support of Ignite[1].
You are need to use method .future(), synchronous result be always null at
this case.
[1]: http://apacheignite.gridgain.org/docs/async-support
On Sat, Nov 5, 2016 at 11:47 PM, Daniel Stieglitz <
dstiegl...@stainlesscode.com> wrote:
>
Hi folks:
We are trying to get messaging working asynchronously. Take a look at the
code below:
IgniteMessaging rmtMsg = grid.message().withAsync();
def future = rmtMsg.send(destination, message);
log.debug("got future ${future}");
That code runs synchronously and the debug says "got future
