Hi Pavel,
I've created a thread.
-Val
On Mon, Sep 6, 2021 at 12:02 PM Pavel Tupitsyn wrote:
> Val,
>
> Would you like me to start the discussion about sync-over-async in Ignite 3
> Java APIs, or do you plan to do it yourself?
>
> On Fri, Sep 3, 2021 at 10:10 PM Valentin Kulichenko <
>
Igniters,
Since there are no more comments, I'm going to merge the first PR later
today and continue working on .NET thin client.
There are separate tickets for CI setup [1] and full API support [2] [3].
[1] https://issues.apache.org/jira/browse/IGNITE-15432
[2]
Val,
Would you like me to start the discussion about sync-over-async in Ignite 3
Java APIs, or do you plan to do it yourself?
On Fri, Sep 3, 2021 at 10:10 PM Valentin Kulichenko <
valentin.kuliche...@gmail.com> wrote:
> Makes sense, thanks!
>
> -Val
>
> On Fri, Sep 3, 2021 at 2:00 AM Pavel
Makes sense, thanks!
-Val
On Fri, Sep 3, 2021 at 2:00 AM Pavel Tupitsyn wrote:
> Hi Val,
>
> This is a very good point.
>
> I've looked around blogs, docs, and system APIs, and updated the IEP
> accordingly:
> For Ignite.NET I propose NOT to add sync methods when the actual
> implementation is
Hi Val,
This is a very good point.
I've looked around blogs, docs, and system APIs, and updated the IEP
accordingly:
For Ignite.NET I propose NOT to add sync methods when the actual
implementation is async:
- It is easy to consume async APIs in C# with async/await keywords (added
in 2012 and
Hi Pavel,
I've looked at the IEP and the public API - looks good to me.
Quick question - do you plan to add sync methods to the interfaces, or
you're thinking to only leave async? If the latter, what are the arguments
for this? The reason I'm asking is that I'm actually thinking about
suggesting
Igniters,
Please review the IEP [1] and the PoC [2] for .NET Thin Client in Ignite
3.0.
[1]
https://cwiki.apache.org/confluence/display/IGNITE/IEP-78+.NET+Thin+Client
[2] https://github.com/apache/ignite-3/pull/306
