C++ Thin client. JVM dependency.

[Nikolay Izhikov-2]

Hello, Igniters.

I have a question from one of an early adopter of Ignite C++ thin client.
Seems, that our C++ thin client depends on JVM lib.

thin-client [1] depends on libignite, and libignite depends on jvm libs [2].

Is that correct?
Why do we need it?
I thought that a thin client is a binary protocol with minimum dependencies.
Do we have the plan to reduce that dependency?

Igor, can you comment on this?

[1] https://github.com/apache/ignite/blob/master/modules/platforms/cpp/thin-client/Makefile.am#L40
[2] https://github.com/apache/ignite/blob/master/modules/platforms/cpp/core/Makefile.am#L30

[Igor Sapego-2]

Hi,

This is not true, thin client does not depend on libignite. It only
depends on libignite-binary and libignite-common. Neither of them
depends on jvm.

Best Regards,
Igor


On Thu, Aug 9, 2018 at 4:16 PM Nikolay Izhikov <[hidden email]> wrote:

> Hello, Igniters.
>
> I have a question from one of an early adopter of Ignite C++ thin client.
> Seems, that our C++ thin client depends on JVM lib.
>
> thin-client [1] depends on libignite, and libignite depends on jvm libs
> [2].
>
> Is that correct?
> Why do we need it?
> I thought that a thin client is a binary protocol with minimum
> dependencies.
> Do we have the plan to reduce that dependency?
>
> Igor, can you comment on this?
>
> [1]
> https://github.com/apache/ignite/blob/master/modules/platforms/cpp/thin-client/Makefile.am#L40
> [2]
> https://github.com/apache/ignite/blob/master/modules/platforms/cpp/core/Makefile.am#L30