Hi guys! Is there any ways to keep asynchronous nature of ignite Service proxy implementation?
The main reason for us to use Services over plain Compute is that we need to spread logic in separate JVM or else we would have to do tedious refactoring in order to avoid dll hell (we use JNI extensively). It looks like under the hood it uses IgniteFuture but"blocks for us". Is there are particular reason for blocking on future.get() ? -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Async-Service-proxy-tp14478.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
