ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pavel Tupitsyn (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-4074) Refactor async (*future) operations in PlatformTarget
Date Mon, 17 Oct 2016 14:01:06 GMT

    [ https://issues.apache.org/jira/browse/IGNITE-4074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15582344#comment-15582344
] 

Pavel Tupitsyn commented on IGNITE-4074:
----------------------------------------

Compute, Messaging, Events, Services, Transactions - done.

> 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)

Mime
View raw message