ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vladimir Ozerov (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-4441) Define plugin API in .NET
Date Thu, 22 Dec 2016 11:55:58 GMT

    [ https://issues.apache.org/jira/browse/IGNITE-4441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15769877#comment-15769877
] 

Vladimir Ozerov commented on IGNITE-4441:
-----------------------------------------

Pavel,
I am a bit concerned about {{IPluginConfiguration.CreateProvider}} method. Ideally user should
not have access to this method. Can we define an attribute on concrete configuration which
will point to a plugin class name?

> 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: Vladimir Ozerov
>              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)

Mime
View raw message