[
https://issues.apache.org/jira/browse/IGNITE-4441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15823996#comment-15823996
]
Pavel Tupitsyn commented on IGNITE-4441:
----------------------------------------
* Refactored plugin startup to use purely .NET mechanism so that {{IIgnite}}
instance is available in all callbacks
* Made sure that when plugin startup fails, all plugins are stopped properly in
reverse order
> 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)
