You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Vladimir Ozerov (JIRA)" <ji...@apache.org> on 2017/01/19 10:13:26 UTC
[jira] [Assigned] (IGNITE-4441) Define plugin API in .NET
[ https://issues.apache.org/jira/browse/IGNITE-4441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vladimir Ozerov reassigned IGNITE-4441:
---------------------------------------
Assignee: Pavel Tupitsyn (was: Vladimir Ozerov)
LGTM
> 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)