Return-Path: X-Original-To: apmail-ignite-dev-archive@minotaur.apache.org Delivered-To: apmail-ignite-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id BB92D17CCE for ; Fri, 11 Sep 2015 12:43:46 +0000 (UTC) Received: (qmail 1029 invoked by uid 500); 11 Sep 2015 12:43:46 -0000 Delivered-To: apmail-ignite-dev-archive@ignite.apache.org Received: (qmail 993 invoked by uid 500); 11 Sep 2015 12:43:46 -0000 Mailing-List: contact dev-help@ignite.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ignite.apache.org Delivered-To: mailing list dev@ignite.apache.org Received: (qmail 773 invoked by uid 99); 11 Sep 2015 12:43:46 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 11 Sep 2015 12:43:46 +0000 Date: Fri, 11 Sep 2015 12:43:46 +0000 (UTC) From: "Vladimir Ozerov (JIRA)" To: dev@ignite.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (IGNITE-1412) .Net: Pass local entry processor pointer to Java. MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Vladimir Ozerov created IGNITE-1412: --------------------------------------- Summary: .Net: Pass local entry processor pointer to Java. Key: IGNITE-1412 URL: https://issues.apache.org/jira/browse/IGNITE-1412 Project: Ignite Issue Type: Task Components: interop Affects Versions: 1.1.4 Reporter: Vladimir Ozerov Fix For: ignite-1.5 Currently we always serialize .Net entry processor and pass only serialized bytes to Java. If processor is to be executed locally, then we pass the same bytes back and deserialize them again. Instead, we can do the following: 1) Serialize entry processor. 2) Allocate handle for it. 3) Pass bytes and handle to Java. 4) In case of local execution, just return back the handle. 5) Once execution is finished, handle can be safely released in "finally" block. This can be easily implemented only for synchronous entry processing. For async mode there is no try/finally. We could release the handle during feature completion, but the problem is that there is no guarantee tha user will ever request this feature. -- This message was sent by Atlassian JIRA (v6.3.4#6332)