NET experience so
> that we could collect them in a single place.
>
>
>
> Incidentally, Pavel’s GitHub page is a good starting point.
>
>
>
>
>
> *From: *Pavel Tupitsyn
> *Sent: *Friday, August 30, 2019 5:34 PM
> *To: *user@ignite.apache.org
> *Subject:
Pavel,
Thanks for details. I am getting some errors shown on console when server
node is started, maybe I will post it in another thread shortly.
Regards
Sudhir
On Friday, August 30, 2019, Pavel Tupitsyn wrote:
> Consuming Ignite in .NET Core is not really different from classic .NET.
>
> As f
pitsyn
> *Sent: *Friday, August 30, 2019 5:34 PM
> *To: *user@ignite.apache.org
> *Subject: *Re: Apache Ignite distributed cache for .Net core web app
>
>
>
> Consuming Ignite in .NET Core is not really different from classic .NET.
>
>
>
> As for web application usage,
Sent: Friday, August 30, 2019 5:34 PM
To: user@ignite.apache.org
Subject: Re: Apache Ignite distributed cache for .Net core web app
Consuming Ignite in .NET Core is not really different from classic .NET.
As for web application usage, there are many scenarios, I can suggest any of
the following
Consuming Ignite in .NET Core is not really different from classic .NET.
As for web application usage, there are many scenarios, I can suggest any
of the following:
1) Start Ignite Server node right in your web app
Pros:
- Simplest development and deployment
- Best performance in cases of small d
Hello!
The link that I have provided has dotnetcore/ dir which hopefully contains
those.
Regards,
--
Ilya Kasnacheev
пт, 30 авг. 2019 г. в 17:06, Sudhir Patil :
> Thanks Ilya, yes I had gone through those git samples.
> I was asking if any other repo for .Net core.
>
> Regards
> Sudhir
>
> On
Thanks Ilya, yes I had gone through those git samples.
I was asking if any other repo for .Net core.
Regards
Sudhir
On Thursday, August 29, 2019, Ilya Kasnacheev
wrote:
> Hello!
>
> 1. They are usually ran as stand alone processes on the designated
> machines. You can probably convert them to w
Hello!
1. They are usually ran as stand alone processes on the designated
machines. You can probably convert them to windows services with some
effort.
2. Client nodes are actually fully functional Ignite distributed topology
nodes. You should start a single client per web application. use it for
