Return-Path: <issues-return-29931-archive-asf-public=cust-asf.ponee.io@ignite.apache.org>
X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io
Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io
Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183])
	by cust-asf2.ponee.io (Postfix) with ESMTP id 22D36200BEE
	for <archive-asf-public-internal@cust-asf2.ponee.io>; Fri, 16 Dec 2016 17:21:00 +0100 (CET)
Received: by cust-asf.ponee.io (Postfix)
	id 1E556160B10; Fri, 16 Dec 2016 16:21:00 +0000 (UTC)
Delivered-To: archive-asf-public@cust-asf.ponee.io
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by cust-asf.ponee.io (Postfix) with SMTP id 69354160B24
	for <archive-asf-public@cust-asf.ponee.io>; Fri, 16 Dec 2016 17:20:59 +0100 (CET)
Received: (qmail 13201 invoked by uid 500); 16 Dec 2016 16:20:58 -0000
Mailing-List: contact issues-help@ignite.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:issues-help@ignite.apache.org>
List-Unsubscribe: <mailto:issues-unsubscribe@ignite.apache.org>
List-Post: <mailto:issues@ignite.apache.org>
List-Id: <issues.ignite.apache.org>
Reply-To: dev@ignite.apache.org
Delivered-To: mailing list issues@ignite.apache.org
Received: (qmail 12994 invoked by uid 99); 16 Dec 2016 16:20:58 -0000
Received: from arcas.apache.org (HELO arcas) (140.211.11.28)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 16 Dec 2016 16:20:58 +0000
Received: from arcas.apache.org (localhost [127.0.0.1])
	by arcas (Postfix) with ESMTP id 6B7802C03E4
	for <issues@ignite.apache.org>; Fri, 16 Dec 2016 16:20:58 +0000 (UTC)
Date: Fri, 16 Dec 2016 16:20:58 +0000 (UTC)
From: "Pavel Tupitsyn (JIRA)" <jira@apache.org>
To: issues@ignite.apache.org
Message-ID: <JIRA.13028630.1481881372000.540437.1481905258437@Atlassian.JIRA>
In-Reply-To: <JIRA.13028630.1481881372000@Atlassian.JIRA>
References: <JIRA.13028630.1481881372000@Atlassian.JIRA> <JIRA.13028630.1481881372244@arcas>
Subject: [jira] [Comment Edited] (IGNITE-4441) Define plugin API in .NET
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394
archived-at: Fri, 16 Dec 2016 16:21:00 -0000


    [ 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)