Return-Path: X-Original-To: apmail-ignite-user-archive@minotaur.apache.org Delivered-To: apmail-ignite-user-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 4319F19719 for ; Fri, 29 Apr 2016 23:42:21 +0000 (UTC) Received: (qmail 13855 invoked by uid 500); 29 Apr 2016 23:42:21 -0000 Delivered-To: apmail-ignite-user-archive@ignite.apache.org Received: (qmail 13799 invoked by uid 500); 29 Apr 2016 23:42:21 -0000 Mailing-List: contact user-help@ignite.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@ignite.apache.org Delivered-To: mailing list user@ignite.apache.org Received: (qmail 13789 invoked by uid 99); 29 Apr 2016 23:42:21 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 29 Apr 2016 23:42:21 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id 85D61C08FB for ; Fri, 29 Apr 2016 23:42:20 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.179 X-Spam-Level: * X-Spam-Status: No, score=1.179 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=2, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamd4-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx2-lw-us.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id zh5MsWNA3hgz for ; Fri, 29 Apr 2016 23:42:19 +0000 (UTC) Received: from mail-oi0-f52.google.com (mail-oi0-f52.google.com [209.85.218.52]) by mx2-lw-us.apache.org (ASF Mail Server at mx2-lw-us.apache.org) with ESMTPS id 6903C5F247 for ; Fri, 29 Apr 2016 23:42:19 +0000 (UTC) Received: by mail-oi0-f52.google.com with SMTP id x201so135888581oif.3 for ; Fri, 29 Apr 2016 16:42:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to; bh=KhDnqKTGkYBMCfpIlq+hmFplp5jMisSVU6cEqO1LjQw=; b=RqVBzD7URew6JPgdg1SoVhb41rV6DJUNOVDehXOqv+14DJC6nKAZ0gf8cSwlOrGrLR s0kii9qXAHJK4zjNsUrh68H5pI+TG4NShrck9XawkKo54ncZdNUlH0HhdBQ+yrc2fAMR FSaXnCaB3NjIOcxCjj7b+s3CLehV7jgdH5plA9kEBEL9pQckmRTaPb9Lz/lyaZCTIGv9 6opHJnPMj5NfPbIHKy5hAoKZQf+RncnKGdmurxlwFXeWobP+WJU+xIF1rhic2Abrgwlx gRpZF2OCyml2uObWRjFtCq4oU5wzf1yIXfP96Mp37OHVF6JaKU9Lztt08+6MeYVOh//p ppjg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:date:message-id:subject:from:to; bh=KhDnqKTGkYBMCfpIlq+hmFplp5jMisSVU6cEqO1LjQw=; b=CW+amXdr+erCj3oFgXILHOWzqCvk7A9BSAi6LGNrrtXKB6KF+aoRzuztDAzm0xusrz a5w9YSlYwn0Ad2XHC7L0YQYa4S7KyiMfx3gKzDYS4TAsaIwd31uKtF0pEwKBfSJ5T9RY 2HWfu7JyeCMXIPExih9djrQ6jmWSLgytGW2vzcpxAdX5voek6ZKgbru1MpMNrnmIeNM7 qpXRqARJbbtdem+yqlGqI3vKfD6lvONTjMfF6MFuxoEcSm17Wq0McUjhp3TQVwcl0uP8 n/TxizdKcrAiSJ3ykkwqJExdtmiBjkpgM3W5ciJPouDUFGbonkJkuaYwzS2LaPSoki7w QmOA== X-Gm-Message-State: AOPr4FV/8a/xeepVddH00NYtNZ7rBNzauZDZAh7KOMjd76XL4VepuQLDszrud/DIj00Mi+u6ytjjHlWfxmKMdg== MIME-Version: 1.0 X-Received: by 10.157.11.8 with SMTP id a8mr10592177ota.82.1461973333668; Fri, 29 Apr 2016 16:42:13 -0700 (PDT) Received: by 10.202.84.70 with HTTP; Fri, 29 Apr 2016 16:42:13 -0700 (PDT) Date: Fri, 29 Apr 2016 19:42:13 -0400 Message-ID: Subject: Ignite support for .net and c++ From: Murthy Kakarlamudi To: user@ignite.apache.org Content-Type: multipart/alternative; boundary=001a113db5243993390531a83101 --001a113db5243993390531a83101 Content-Type: text/plain; charset=UTF-8 Ignite gurus, My application consists of .net and c++ components. Currently we use shared database pattern to exchange data across the components. As our volume is pretty huge, we were looking for an in-memory solution and Ignite Data Grid with write behind support seemed like a perfect match for our requirements. I have been trying to create a simple poc where in .net and c++ components will be able to access ignite cache simultaneously. I been trying to create this for the past couple of weeks and running into a lot of errors. Individually .net and c++ components work fine, but when I spin up both the nodes, running into a lot of issues. Can you please let me know if Ignite Datagrid is the right choice for my use case. If so are there any examples or reference projects that had .net and c++ running together that will of tremendous help to me. Thanks for your valuable support, Murthy. --001a113db5243993390531a83101 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Ignite gurus,
=C2=A0 =C2=A0 =C2=A0My application consi= sts of .net and c++ components. Currently we use shared database pattern to= exchange data across the components. As our volume is pretty huge, we were= looking for an in-memory solution and Ignite Data Grid with write behind s= upport seemed like a perfect match for our requirements.=C2=A0
= =C2=A0 =C2=A0 =C2=A0I have been trying to create a simple poc where in .net= and c++ components will be able to access ignite cache simultaneously. I b= een trying to create this for the past couple of weeks and running into a l= ot of errors. Individually .net and c++ components work fine, but when I sp= in up both the nodes, running into a lot of issues.
=C2=A0 =C2=A0= =C2=A0Can you please let me know if Ignite Datagrid is the right choice fo= r my use case. If so are there any examples or reference projects that had = .net and c++ running together that will of tremendous help to me.

Thanks for your valuable support,
Murthy.=C2=A0
--001a113db5243993390531a83101--