[
https://issues.apache.org/jira/browse/IGNITE-4074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15574620#comment-15574620
]
Pavel Tupitsyn commented on IGNITE-4074:
----------------------------------------
Refactoring is needed in:
* Compute: only ExecuteJavaTaskAsync, other methods use different mechanism
* Cache (27 methods)
* Messaging (2 methods)
* Events (6 methods)
* Services (7 methods)
* Transactions (2 methods)
> Refactor async (*future) operations in PlatformTarget
> -----------------------------------------------------
>
> Key: IGNITE-4074
> URL: https://issues.apache.org/jira/browse/IGNITE-4074
> Project: Ignite
> Issue Type: Sub-task
> Components: platforms
> Reporter: Pavel Tupitsyn
> Assignee: Pavel Tupitsyn
> Labels: .NET
> Fix For: 1.8
>
>
> Currently async operations are executed in two steps:
> - start an operation (Cache.Get)
> - get the future (UU.TargetListenFuture* methods)
> This separation is unnecessary. See if we can perform asyn operations in one
> JNI call. See how PlatformCache.OP_REBALANCE does this.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
