ignite-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Igor Sapego <isap...@apache.org>
Subject Re: Reason for using JVM Instance for Ignite C++ Driver
Date Thu, 16 Nov 2017 10:23:24 GMT

This is because Ignite C++ is not just thin client. It is actually a node,
that can be a server node and can join topology. You can actually
store data on it, run queries and compute jobs over it, and so on.

Does it answer your question?

Best Regards,

On Thu, Nov 16, 2017 at 10:08 AM, kotamrajuyashasvi <
kotamrajuyashasvi@gmail.com> wrote:

> Hi
> From the Ignite Docs: Ignite ะก++ starts the JVM in the same process and
> communicates with it via JNI. I would like to know why a JVM instance is
> required? Why can't we have Ignite C++ driver communicate via TCP directly
> to the Ignite Server and from the server side process the request and
> perform necessary actions. In the end the Client being able to communicate
> to the server is all what matters right.
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/

View raw message