[ 
https://issues.apache.org/jira/browse/IGNITE-23651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pavel Tupitsyn updated IGNITE-23651:
------------------------------------
    Description: 
As a user, I want to integrate Ignite 3 .NET client into my ASP.NET and Hosted 
Service applications using standard dependency injection infrastructure 
(*IServiceCollection*).

Currently, it is not clear how to do that properly:
* *IgniteClient.StartAsync* is asynchronous, and DI factory methods must be 
synchronous - what to do?
* Should I use Scoped or Singleton?

As Ignite developers, we recommend using a single *IgniteClient* instance, or a 
pool of clients, but this requires non-trivial setup.

We should provide an *IgniteClientPool* implementation, and *ServiceCollection* 
extension methods to make it easy for the users.

  was:As a user, I want to integrate Ignite 3 .NET client into my ASP.NET and 
Hosted Service applications using standard dependency injection infrastructure 
(*IServiceCollection*).


> .NET: Thin 3.0: Add ServiceCollection extensions for DI integration
> -------------------------------------------------------------------
>
>                 Key: IGNITE-23651
>                 URL: https://issues.apache.org/jira/browse/IGNITE-23651
>             Project: Ignite
>          Issue Type: Improvement
>          Components: platforms, thin client
>            Reporter: Pavel Tupitsyn
>            Assignee: Pavel Tupitsyn
>            Priority: Major
>              Labels: .NET, ignite-3
>             Fix For: 3.1
>
>
> As a user, I want to integrate Ignite 3 .NET client into my ASP.NET and 
> Hosted Service applications using standard dependency injection 
> infrastructure (*IServiceCollection*).
> Currently, it is not clear how to do that properly:
> * *IgniteClient.StartAsync* is asynchronous, and DI factory methods must be 
> synchronous - what to do?
> * Should I use Scoped or Singleton?
> As Ignite developers, we recommend using a single *IgniteClient* instance, or 
> a pool of clients, but this requires non-trivial setup.
> We should provide an *IgniteClientPool* implementation, and 
> *ServiceCollection* extension methods to make it easy for the users.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to