Re: Node.js Thin Client @ npmjs

Hi Dmitriy, Agree, your proposal makes a lot of sense. p. On Fri, May 25, 2018 at 11:04 AM, Dmitriy Setrakyan wrote: > I generally think that as a community we need to start taking an approach > of separate thin client releases. This goes for Java, .NET, JDBC, ODBC, >

Re: Node.js Thin Client @ npmjs

I generally think that as a community we need to start taking an approach of separate thin client releases. This goes for Java, .NET, JDBC, ODBC, Node.JS, etc... We can still host them in the same Ignite repo, but they should be a separate download. Of course, they should be included in the

Re: Node.js Thin Client @ npmjs

As Denis said, there is no need to download the entire Ignite repo to install the client. Once published the client is going to be installed by users with a command: npm install -g apache-ignite-client The sources are going to be distributed as a part of the ignite repository, yes. But in

Re: Node.js Thin Client @ npmjs

Once the client is built it will be uploaded to the npmjs repository, right? So, a JS developer can download the client from there without touching the whole Ignite binary release. However, those who download the whole Ignite binary distribution will find node.js there (as well as .NET, C++, JDBC

Re: Node.js Thin Client @ npmjs

On Thu, May 24, 2018 at 12:36 PM, Pavel Petroshenko wrote: > Fair enough. Consistency with the other clients is a good argument. > > Pavel, I would discuss it a bit more. Does it really make sense for a node.js user to download the whole Ignite distribution just to get a

Re: Node.js Thin Client @ npmjs

Fair enough. Consistency with the other clients is a good argument. p. On Thu, May 24, 2018 at 11:44 AM, Dmitriy Setrakyan wrote: > On Thu, May 24, 2018 at 11:42 AM, Igor Sapego wrote: > > > Well, all other clients have the same version as Ignite. >

Re: Node.js Thin Client @ npmjs

On Thu, May 24, 2018 at 11:42 AM, Igor Sapego wrote: > Well, all other clients have the same version as Ignite. > Are there any reasons to make a Node.js client some > kind of a special case? > > I may have spoken too soon. Do we plan to include the node.js client into Ignite

Re: Node.js Thin Client @ npmjs

Well, all other clients have the same version as Ignite. Are there any reasons to make a Node.js client some kind of a special case? Best Regards, Igor On Thu, May 24, 2018 at 8:21 PM, Dmitriy Setrakyan wrote: > On Thu, May 24, 2018 at 10:03 AM, Pavel Petroshenko

Re: Node.js Thin Client @ npmjs

On Thu, May 24, 2018 at 10:03 AM, Pavel Petroshenko wrote: > Igor, > > Are you proposing to update the Thin Client versions on every Ignite > release regardless of the changes made to them? > > I tend to think that an independent versioning scheme for the Thin Clients >

Re: Node.js Thin Client @ npmjs

Igor, Are you proposing to update the Thin Client versions on every Ignite release regardless of the changes made to them? I tend to think that an independent versioning scheme for the Thin Clients might be more flexible/meaningful. p. On Thu, May 24, 2018 at 2:04 AM, Igor Sapego

Re: Node.js Thin Client @ npmjs

1. Sounds OK for me. 2. Since Node.js client is going to be included in Ignite releases, I guess it make sense to align its version with the version of Ignite, i.e. 2.6, etc... Best Regards, Igor On Thu, May 24, 2018 at 9:02 AM, Pavel Petroshenko wrote: >