ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pavel Tupitsyn (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (IGNITE-4441) Define plugin API in .NET
Date Fri, 16 Dec 2016 16:20:58 GMT

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

Pavel Tupitsyn edited comment on IGNITE-4441 at 12/16/16 4:20 PM:
------------------------------------------------------------------

On the second thought, we should not examine all DLLs in the folder.
* Scanning all assemblies in a folder is unsafe and slow
* User may want to load specific plugins only, or decide dynamically which ones should be
loaded

So the proper way is to specify a list of {{IPluginProvider}} implementations via {{ICollection<Type>
IgniteConfiguration.Plugins}}.
This requires one extra step from the user, but allows precise control. 

We can combine this with {{IgniteConfiguration.PluginConfigurations}}, so that plugin author
provides {{IPluginConfiguration}} implementation with {{PluginProviderType}} property already
set.


was (Author: ptupitsyn):
On the second thought, we should not examine all DLLs in the folder.
* Scanning all assemblies in a folder is unsafe and slow
* User may want to load specific plugins only, or decide dynamically which ones should be
loaded

So the proper way is to specify a list of {{IPluginProvider}} implementations via {{ICollection<Type>
IgniteConfiguration.Plugins}}.
This requires one extra step from the user, but allows precise control.

> 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}}
> * {{CacheConfiguration.PluginConfigurations}}
> * {{IPluginProvider}}
> * {{ICachePluginProvider}}
> * {{IPluginContext}}
> * {{ICachePluginContext}}
> 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