Mailing-List: contact issues-help@ignite.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ignite.apache.org
Date: Fri, 11 Sep 2015 12:59:45 +0000 (UTC)
From: "Vladimir Ozerov (JIRA)" <jira@apache.org>
To: issues@ignite.apache.org
Message-ID: <JIRA.12863374.1441976379000.313671.1441976385848@Atlassian.JIRA>
In-Reply-To: <JIRA.12863374.1441976379000@Atlassian.JIRA>
References: <JIRA.12863374.1441976379000@Atlassian.JIRA>
 <JIRA.12863374.1441976379687@arcas>
Subject: [jira] [Created] (IGNITE-1414) .Net: support async/await in the API
 via extension methods
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Vladimir Ozerov created IGNITE-1414:
---------------------------------------

             Summary: .Net: support async/await in the API via extension methods
                 Key: IGNITE-1414
                 URL: https://issues.apache.org/jira/browse/IGNITE-1414
             Project: Ignite
          Issue Type: Task
          Components: interop
    Affects Versions: 1.1.4
            Reporter: Vladimir Ozerov
             Fix For: ignite-1.5


Currently to get awaitable target (Task) for async operation, user have to do the following (pseudocode):
{code}
target.ExecuteOperation();

IFuture fut = target.CurrentFuture();

Task task = fut.ToTask();
{code}

This is too complex. We need to think how to minimize this boilerplate code. Extensions + lambdas appears to be good candidates for this. E.g.:
{code}
Task task = target.DoAsync(t => t.Execute());
{code}


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