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-1652) .Net: Rework async APIs (remove WithAsync/GetFuture)
Date Mon, 26 Oct 2015 13:50:27 GMT

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

Pavel  Tupitsyn commented on IGNITE-1652:
-----------------------------------------

Let's hide IFuture and return Tasks directly to have a .Net-friendly API.
Later we can improve Task creation performance: https://issues.apache.org/jira/browse/IGNITE-1791

> .Net: Rework async APIs (remove WithAsync/GetFuture)
> ----------------------------------------------------
>
>                 Key: IGNITE-1652
>                 URL: https://issues.apache.org/jira/browse/IGNITE-1652
>             Project: Ignite
>          Issue Type: Task
>          Components: interop
>    Affects Versions: 1.5
>            Reporter: Pavel  Tupitsyn
>            Assignee: Pavel  Tupitsyn
>             Fix For: 1.5
>
>
> {code}
> cache.WithAsync().Get();
> var future = cache.GetFuture();
> {code}
> should become
> {code}
> var future = cache.GetAsync();
> {code}
> See if we can make ToTask() more efficient, or even get rid of Futures completely in
favor of tasks, preserving performance.
> First step is .Net-only (remove GetFuture from public API, call it inside *Async methods).
This requires 2 JNI calls.
> Later we should look into making it a single JNI call.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message