Re: c++ native client

e.incubator.apache.org > Subject: Re: c++ native client > > The native client in geode will likely be v1 to match the Java bits, or > whatever geode version is when nc is ready to release with geode. > On Fri, Jun 3, 2016 at 7:18 AM Dor Ben Dov <dor.ben-...@amdocs.com> wro

RE: c++ native client

@geode.incubator.apache.org Subject: Re: c++ native client The native client in geode will likely be v1 to match the Java bits, or whatever geode version is when nc is ready to release with geode. On Fri, Jun 3, 2016 at 7:18 AM Dor Ben Dov <dor.ben-...@amdocs.com> wrote: > Hi, > > Anyone can tell me what

Re: c++ native client

The native client in geode will likely be v1 to match the Java bits, or whatever geode version is when nc is ready to release with geode. On Fri, Jun 3, 2016 at 7:18 AM Dor Ben Dov wrote: > Hi, > > Anyone can tell me what is the version of the native client (c++) ? > >

c++ native client

Hi, Anyone can tell me what is the version of the native client (c++) ? Dor This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement, you may review at http://www.amdocs.com/email_disclaimer.asp

Re: c++ native client memory management

We do not use an external memory manager. On Tue, May 31, 2016 at 8:14 AM Gal Palmery wrote: > Hi, > > Do you use a specific external memory manager (like mtmalloc, hoard, > etc..) for native-client code? > > Thanks, > Gal > > This message and the information contained

c++ native client memory management

Hi, Do you use a specific external memory manager (like mtmalloc, hoard, etc..) for native-client code? Thanks, Gal This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement, you may review at