[ https://issues.apache.org/jira/browse/IGNITE-4441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15761416#comment-15761416 ]
ASF GitHub Bot commented on IGNITE-4441: ---------------------------------------- GitHub user ptupitsyn opened a pull request: https://github.com/apache/ignite/pull/1362 IGNITE-4441 Define plugin API in .NET You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-4441 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/1362.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #1362 ---- ---- > Define plugin API in .NET > ------------------------- > > Key: IGNITE-4441 > URL: https://issues.apache.org/jira/browse/IGNITE-4441 > Project: Ignite > Issue Type: Sub-task > Components: platforms > Reporter: Pavel Tupitsyn > Assignee: Pavel Tupitsyn > Labels: .NET > Fix For: 2.0 > > > Define plugin API in .NET similar to Java API: > * {{IgniteConfiguration.PluginConfigurations}} > * {{IPluginProvider}} > * {{IPluginContext}} > Should work like this: > * Plugin author implements {{IPluginProvider}} > * We discover plugins on Ignite start by examining all DLL files in the > folder, load DLLs where {{IPluginProvider}} implementations are present, > instantiate these implementations, and call > {{IPluginProvider.Start(IPluginContext)}} method. > * Plugin user can retrieve plugin via {{IIgnite.GetPlugin<T>(string name)}}, > or via helper extension method provided by plugin author. > This task does not include the possibility to interact with Java from the > plugin code. -- This message was sent by Atlassian JIRA (v6.3.4#6332)