On Mon, Jun 18, 2018 at 9:45 AM, Denis Magda wrote:
> Guys,
>
> Have a look at Hazelcast. They provide both approaches - installation with
> a package management system + binary (or zip archives downloads):
> https://hazelcast.org/clients-languages/
>
> It will be great to provide Ignite
stalled from source code repo, etc.:
> > >
> > > go get -u github.com/amsokol/ignite-go-client
> > >
> > > So the proposal is not really applicable to Go lang client.
> > >
> > > Thanks,
> > > Aleksandr
> > >
> > > From:
; >
> > Thanks,
> > Aleksandr
> >
> > From: Pavel Petroshenko
> > Sent: 16 июня 2018 г. 21:10
> > To: Denis Magda
> > Cc: dev
> > Subject: Re: Separate binaries for thin clients and drivers
> >
> > Hi Denis,
> >
> > There are
> Thanks,
> Aleksandr
>
> From: Pavel Petroshenko
> Sent: 16 июня 2018 г. 21:10
> To: Denis Magda
> Cc: dev
> Subject: Re: Separate binaries for thin clients and drivers
>
> Hi Denis,
>
> There are no "binaries" for Node.js and Python that you c
. 21:10
To: Denis Magda
Cc: dev
Subject: Re: Separate binaries for thin clients and drivers
Hi Denis,
There are no "binaries" for Node.js and Python that you can download. These
Thin Clients are distributed and installed by a package management system
(npm, pip): which resolves all the de
Pavel, this makes sense. In a way, these clients already have a separate
binary installation.
D.
On Sat, Jun 16, 2018, 11:10 Pavel Petroshenko wrote:
> Hi Denis,
>
> There are no "binaries" for Node.js and Python that you can download. These
> Thin Clients are distributed and installed by a
+1
On Fri, Jun 15, 2018 at 12:29 PM, Denis Magda wrote:
> Igniters,
>
> Presently, all our thin clients and SQL drivers are stored in the main
> Ignite repository. That's totally fine, I wouldn't change anything in here.
>
> But, what I would encourage us to contemplate on is how a user gets
