Re: Native .NET

[vkulichenko <va...@gmail.com>]

ignite_mk,


ignite_mk wrote
> Based on what i understand, the .NET client(windows desktop for example),
> needs a JVM runtime installed?
> 
> This may not be a good idea, in my opinion. This will cause a lot of
> maintenance (think upgrades) and security concerns. 
> 
> Please advise if there is an "option" for keeping this a "pure" native
> .NET implementation, without any Java runtime dependency.

No, there is no such option. Such an implementation will obviously require
tons of new code that has to be maintained separately, so it doesn't make
much sense. Could you please describe your concerns in more details? What is
wrong with the current implementation from your point of view?

Also, please properly subscribe to the mailing list so that community
receives email notifications. Just follow this simple instruction:
http://apache-ignite-users.70518.x6.nabble.com/mailing_list/MailingListOptions.jtp?forum=1

-Val



--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Native-NET-tp1689p2374.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Native .NET

[vkulichenko <va...@gmail.com>]

ignite_mk,

I don't think you have to package it, it's just a requirement for
environment, similar to .NET runtime. Ignite can work on any version of JDK7
or JDK8, there is no reason to upgrade each time new Java is released.

-Val



--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Native-NET-tp1689p2404.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Native .NET

[ignite_mk <JU...@gmail.com>]

As i mentioned, the main concern is the requirement of having a JRE on the
client (windows desktop). If it was native, we wouldn't have to worry about
packaging that JRE and upgrading it whenever there is an updated version of
Java.



--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Native-NET-tp1689p2400.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.