From dev-return-30105-archive-asf-public=cust-asf.ponee.io@ignite.apache.org Tue Jan 16 11:05:18 2018 Return-Path: X-Original-To: archive-asf-public@eu.ponee.io Delivered-To: archive-asf-public@eu.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by mx-eu-01.ponee.io (Postfix) with ESMTP id EFC9A18065B for ; Tue, 16 Jan 2018 11:05:17 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id DF9B1160C34; Tue, 16 Jan 2018 10:05:17 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 5906D160C26 for ; Tue, 16 Jan 2018 11:05:17 +0100 (CET) Received: (qmail 15401 invoked by uid 500); 16 Jan 2018 10:05:16 -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 15384 invoked by uid 99); 16 Jan 2018 10:05:16 -0000 Received: from mail-relay.apache.org (HELO mail-relay.apache.org) (140.211.11.15) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 16 Jan 2018 10:05:16 +0000 Received: from mail-qk0-f172.google.com (mail-qk0-f172.google.com [209.85.220.172]) by mail-relay.apache.org (ASF Mail Server at mail-relay.apache.org) with ESMTPSA id 18A931A00E2 for ; Tue, 16 Jan 2018 10:05:16 +0000 (UTC) Received: by mail-qk0-f172.google.com with SMTP id d18so20148518qke.7 for ; Tue, 16 Jan 2018 02:05:16 -0800 (PST) X-Gm-Message-State: AKwxytc8bkZRGzAdAXJsCJwkwqLf3uzNcbqvHS3KZagel78972S1i1ej ca4pEIwYrRaz11fuU0Wkzxe3WZwD3cZqX2sLH01Zgg== X-Google-Smtp-Source: ACJfBouaK8ydFBs0r8UDeURLYJcNzRFuHFs9TacftvUT17Sht2y961aRM6bNjgiEbQXMvmRGKSZHof3myOipwB4m6E4= X-Received: by 10.55.22.29 with SMTP id g29mr51176320qkh.26.1516097114120; Tue, 16 Jan 2018 02:05:14 -0800 (PST) MIME-Version: 1.0 Received: by 10.140.36.133 with HTTP; Tue, 16 Jan 2018 02:04:33 -0800 (PST) In-Reply-To: References: <1516089806779-0.post@n4.nabble.com> From: Dmitriy Setrakyan Date: Tue, 16 Jan 2018 02:04:33 -0800 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: Thin client: Java bindings To: dev@ignite.apache.org Content-Type: multipart/alternative; boundary="001a11479f50eeb6140562e1dd1b" --001a11479f50eeb6140562e1dd1b Content-Type: text/plain; charset="UTF-8" Got it, thanks! On Tue, Jan 16, 2018 at 2:02 AM, Alexey Kukushkin wrote: > Dmitriy, > > Although having invoke() was really important for us, implementing invoke() > does not look trivial (need to think about real multi-lingual and > cross-platform design) and we do not have time to implement it on the first > phase. Currently thin client protocol does not support it so we would have > to design it ourselves. Still we will need invoke and transactions on the > next phases and really appreciate if community would design something to > support it in the binary protocol. > --001a11479f50eeb6140562e1dd1b--