.NET: Update README regarding C++ interop and thin client

Project: http://git-wip-us.apache.org/repos/asf/ignite/repo
Commit: http://git-wip-us.apache.org/repos/asf/ignite/commit/eee4f17b
Tree: http://git-wip-us.apache.org/repos/asf/ignite/tree/eee4f17b
Diff: http://git-wip-us.apache.org/repos/asf/ignite/diff/eee4f17b

Branch: refs/heads/ignite-7485-2
Commit: eee4f17b1ad8edbb8cfaf7ba7902c30a83a236d0
Parents: 71db707
Author: Pavel Tupitsyn <ptupit...@apache.org>
Authored: Fri Feb 2 15:01:27 2018 +0300
Committer: Pavel Tupitsyn <ptupit...@apache.org>
Committed: Fri Feb 2 15:01:27 2018 +0300

 modules/platforms/dotnet/README.md | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/modules/platforms/dotnet/README.md 
index f1cb989..4830940 100644
--- a/modules/platforms/dotnet/README.md
+++ b/modules/platforms/dotnet/README.md
@@ -75,11 +75,13 @@ Ignite is an elastic, horizontally scalable distributed 
system that supports add
 ## Ignite and Ignite.NET
 * Ignite.NET is built on top of Ignite.
-* .NET starts the JVM in the same process and communicates with it via JNI & 
+* .NET starts the JVM in the same process and communicates with it via JNI.
 * .NET, C++ and Java nodes can join the same cluster, use the same caches, and 
interoperate using common binary protocol.
 * Java compute jobs can execute on any node (Java, .NET, C++).
 * .NET compute jobs can only execute on .NET nodes.
+Ignite.NET also has Thin Client mode (see `Ignition.StartClient()`), which 
does not start JVM and does not require Java on machine.
 ## Ignite Components
 You can view Apache Ignite as a collection of independent, well-integrated 
components geared to improve performance and

Reply via email to