Yes, we need to add it to all thin clients, actually, and to thin protocol specification.
On the second thought, we need to implement second approach anyway, as Ignite can be configured with XML. So, I'd stopped on the second approach for now, as we will need it in any way. Best Regards, Igor On Tue, Jan 22, 2019 at 6:19 PM ppenguin <[email protected]> wrote: > Hi，Do we need to add it into the thin cpp client too?If so, I think we’d > better choose the first method,then we can reuse the code. > > > ------------------ Original ------------------ > From: Igor Sapego <[email protected]> > Date: 周一,1月 21,2019 11:19 下午 > To: dev <[email protected]> > Subject: Re: IGNITE-8283 CPP: Implement 'varint' solution to be > configurable via BinaryConfiguration > > > > Hi, > > The obvious solution here is to add IgniteConfiguration class for C++, but > it looks like not an easy task. > > There is another solution which is more easy to implement: it is to add > call > to Java code, something like "isVarintActive()", which is going to be > called > on node startup. > Best Regards, > Igor > > > > On Mon, Jan 21, 2019 at 1:40 PM ppenguin <[email protected]> > wrote: > > > Igniters, > > > > I'am beginning with this task. Now the c++ implementation lacks some > parts > > that existed in Java and C#, so the task seems a little complex. I want > to > > discuss the details here.
