Plugins/de - Revision history

Djphil: Fix Quicklinks

2020-10-19T16:07:35Z

Fix Quicklinks

Manni at 19:35, 13 April 2018

2018-04-13T19:35:41Z

Manni: /* Connectors */

2018-04-13T19:34:05Z

‎Connectors

Manni: /* Specifying Plugin Implementation in the Configuration */

2018-04-13T19:30:25Z

‎Specifying Plugin Implementation in the Configuration

Manni: /* Unused Extension Points */

2018-04-13T19:28:53Z

‎Unused Extension Points

Manni: /* Dynamic Plugins with Mono.Addins */

2018-04-13T19:25:29Z

‎Dynamic Plugins with Mono.Addins

Manni: /* Overview */

2018-04-13T19:19:35Z

‎Overview

Manni: Created page with "==Overview== OpenSimulator uses several mechanisms to enable dynamic configuration of functionality. This page describes these mechanisms. == Dynamic Plugins with Mono.Addin..."

2018-04-13T19:18:53Z

Created page with "==Overview== OpenSimulator uses several mechanisms to enable dynamic configuration of functionality. This page describes these mechanisms. == Dynamic Plugins with Mono.Addin..."

New page

==Overview==

OpenSimulator uses several mechanisms to enable dynamic configuration of functionality. This page describes these mechanisms.

== Dynamic Plugins with Mono.Addins ==

Some types of plugins are discovered at runtime using '''Extension Points''', and loaded using '''Mono.Addins'''. This mechanism is described in detail [[How to create a dynamic plugin|here]] and [[Dynamic Plugin Quickstart|here]].

These types of plugins are used when it's desirable to load '''all''' the plugins of a particular type.

This mechanism is currently used in the following cases:

'''/OpenSim/Startup''' - application plugins (IApplicationPlugin). Loaded by OpenSimBase when OpenSimulator starts. The plugins are loaded using PluginLoader.

'''/OpenSim/RegionModules''' - region modules. Loaded by RegionModulesControllerPlugin, which is itself an application plugin. The plugins are loaded by calling AddinManager directly (not through PluginLoader).

'''/OpenSim/WindModule''' - wind models. Loaded by WindModule, which is itself a region module. The plugins are loaded by calling AddinManager directly.

==== Unused Extension Points ====

There are some extension points defined that are never actually loaded. For example, OpenSim.data.MySQL.addin.xml defines plugins that '''provide''' implementations for extension points such as "/OpenSim/GridData" and "/OpenSim/AssetData". However, no-one actually loads these extension points (as far as I can see). Instead, these plugins are loaded using the config-files technique described below.

These points have been removed in OpenSimulator code after 0.7.1.1.

== Specifying Plugin Implementation in the Configuration ==

For most plugins, the class that should be used to implement the plugin's interface is specified explicitly in one of the .INI files. The application then simply loads the assembly (DLL); finds the specified class; and instantiates it.

These types of plugins are used when it only makes sense to load a single implementation of the plugin; not all the available implementations. For example, only one database access module can be used. Therefore, the .INI files contain directives such as these:

[DatabaseService]
StorageProvider = "OpenSim.Data.MySQL.dll"

Sometimes the definition also specifies which class to use. For example:

[InventoryService]
LocalServiceModule = "OpenSim.Services.InventoryService.dll:XInventoryService"

Let's take the example of the data-access plugin further. Most classes that need to access the database have a Data interface defined. For example, PresenseService defines IPresenceData. This interface has implementations for all of the databases OpenSimulator supports. When the service starts, it loads the database assembly that was specified in the configuration, and then finds in that assembly the class that implements the desired interface (IPresenceData). The code looks something like this (although this is simplified):

IConfig dbConfig = config.Configs["DatabaseService"];
string dllName = dbConfig.GetString("StorageProvider");
IPresenceData m_Database = LoadPlugin<IPresenceData>(dllName);

== Connectors ==

Robust finds and loads its [[Connectors]] by having them specified explicitly in Robust.ini (in the "ServiceConnectors" entry). Since the plugins are specified explicitly, this works by loading the DLL's manually. However, it's somewhat similar to the Mono.Addins technique in that Robust loads '''all''' the connectors specified; not just one. Perhaps it can be refactored someday to truly use Mono.Addins.

The connectors are loaded by calling ServerUtils.LoadPlugin<IServiceConnector>().

← Older revision		Revision as of 16:07, 19 October 2020
Line 1:		Line 1:
−	{{Quicklinks\|~~Download~~}}{{ReleaseInfo}}	+	{{Quicklinks\|Plugins}}
		+
		+	{{ReleaseInfo}}
		+
	==Überblick==		==Überblick==

← Older revision		Revision as of 19:35, 13 April 2018
Line 1:		Line 1:
		+	{{Quicklinks\|Download}}{{ReleaseInfo}}
	==Überblick==		==Überblick==

Line 50:		Line 51:

	Die Connectors werden durch den Aufruf von ServerUtils.LoadPlugin<IServiceConnector>() geladen.		Die Connectors werden durch den Aufruf von ServerUtils.LoadPlugin<IServiceConnector>() geladen.
		+
		+	[[Category:Users]]
		+	[[Category:Developers]]
		+	[[Category:German Translations]]

@@ Line 18: / Line 18: @@
 '''/OpenSim/WindModule''' - Windmodelle . Geladen von WindModule, welches selbst ein Regionalmodul ist. Die Plugins werden durch direkten Aufruf von AddinManager geladen.
-==== Unused Extension Points ====
+==== Unbenutzte Erweiterungspunkte ====
-There are some extension points defined that are never actually loaded. For example, OpenSim.data.MySQL.addin.xml defines plugins that '''provide''' implementations for extension points such as "/OpenSim/GridData" and "/OpenSim/AssetData". However, no-one actually loads these extension points (as far as I can see). Instead, these plugins are loaded using the config-files technique described below.
+Es sind einige Erweiterungspunkte definiert, die niemals tatsächlich geladen werden. Zum Beispiel definiert OpenSim.data.MySQL.addin.xml Plugins, die Implementierungen für Erweiterungspunkte wie "/OpenSim/GridData" und "/OpenSim/AssetData" bereitstellen. Allerdings lädt tatsächlich niemand diese Erweiterungspunkte (soweit ich sehen kann). Stattdessen werden diese Plugins mit der unten beschriebenen Config-Files-Methode geladen.
-These points have been removed in OpenSimulator code after 0.7.1.1.
+Diese Punkte wurden nach 0.7.1.1 im OpenSimulator-Code entfernt.
 == Specifying Plugin Implementation in the Configuration ==

@@ Line 45: / Line 45: @@
   IPresenceData m_Database = LoadPlugin<IPresenceData>(dllName);
-== Connectors ==
+== Anschlüsse ==
-Robust finds and loads its [[Connectors]] by having them specified explicitly in Robust.ini (in the "ServiceConnectors" entry). Since the plugins are specified explicitly, this works by loading the DLL's manually. However, it's somewhat similar to the Mono.Addins technique in that Robust loads '''all''' the connectors specified; not just one. Perhaps it can be refactored someday to truly use Mono.Addins.
+Robust sucht und lädt seine [[Connectors]], indem sie in der Datei Robust.ini (im Eintrag "ServiceConnectors") explizit angegeben werden. Da die Plugins explizit angegeben werden, funktioniert dies, indem die DLLs manuell geladen werden. Es ähnelt jedoch der Mono.Addins-Methode insofern, als Robust loads '''all''' angegebenen Anschlüsse lädt. nicht nur einer. Vielleicht kann es irgendwann überarbeitet werden, um wirklich Mono.Addins zu verwenden.
-The connectors are loaded by calling ServerUtils.LoadPlugin<IServiceConnector>().
+Die Connectors werden durch den Aufruf von ServerUtils.LoadPlugin<IServiceConnector>() geladen.

@@ Line 24: / Line 24: @@
 Diese Punkte wurden nach 0.7.1.1 im OpenSimulator-Code entfernt.
-== Specifying Plugin Implementation in the Configuration ==
+== Angeben der Plugin-Implementierung in der Konfiguration ==
-For most plugins, the class that should be used to implement the plugin's interface is specified explicitly in one of the .INI files. The application then simply loads the assembly (DLL); finds the specified class; and instantiates it.
+Bei den meisten Plugins wird die Klasse, die zur Implementierung der Plugin-Schnittstelle verwendet werden soll, explizit in einer der INI-Dateien angegeben. Die Anwendung lädt dann einfach die Assembly (DLL); findet die angegebene Klasse; und instanziiert es.
-These types of plugins are used when it only makes sense to load a single implementation of the plugin; not all the available implementations. For example, only one database access module can be used. Therefore, the .INI files contain directives such as these:
+Diese Plugins werden verwendet, wenn es nur sinnvoll ist, eine einzige Implementierung des Plugins zu laden; nicht alle verfügbaren Implementierungen. Zum Beispiel kann nur ein Datenbankzugriffsmodul verwendet werden. Daher enthalten die INI-Dateien Anweisungen wie diese:
   [DatabaseService]
      StorageProvider = "OpenSim.Data.MySQL.dll"
-Sometimes the definition also specifies which class to use. For example:
+Manchmal gibt die Definition auch an, welche Klasse verwendet werden soll. Beispielsweise:
   [InventoryService]
@@ Line 39: / Line 39: @@
-Let's take the example of the data-access plugin further. Most classes that need to access the database have a Data interface defined. For example, PresenseService defines IPresenceData. This interface has implementations for all of the databases OpenSimulator supports. When the service starts, it loads the database assembly that was specified in the configuration, and then finds in that assembly the class that implements the desired interface (IPresenceData). The code looks something like this (although this is simplified):
+Nehmen wir das Beispiel des Datenzugriffs-Plugins weiter. Für die meisten Klassen, die auf die Datenbank zugreifen müssen, ist eine Datenschnittstelle definiert. Zum Beispiel definiert PresenseService IPresenceData. Diese Schnittstelle verfügt über Implementierungen für alle Datenbanken, die OpenSimulator unterstützt. Wenn der Dienst gestartet wird, lädt er die Datenbankassembly, die in der Konfiguration angegeben wurde, und sucht dann in dieser Assembly die Klasse, die die gewünschte Schnittstelle implementiert (IPresenceData). Der Code sieht ungefähr so aus (obwohl dies vereinfacht ist):
   IConfig dbConfig = config.Configs["DatabaseService"];

@@ Line 3: / Line 3: @@
 OpenSimulator verwendet verschiedene Mechanismen, um die dynamische Konfiguration von Funktionen zu ermöglichen. Diese Seite beschreibt diese Mechanismen.
-== Dynamic Plugins with Mono.Addins ==
+== Dynamische Plugins mit Mono.Addins ==
-Some types of plugins are discovered at runtime using '''Extension Points''', and loaded using '''Mono.Addins'''. This mechanism is described in detail [[How to create a dynamic plugin|here]] and [[Dynamic Plugin Quickstart|here]].
+Einige Plugins werden zur Laufzeit mit '''Extension Points''' erkannt und mit '''Mono.Addins''' geladen. Dieser Mechanismus wird [[How to create a dynamic plugin|hier]] und [[Dynamic Plugin Quickstart|hier]] detailliert beschrieben.
-These types of plugins are used when it's desirable to load '''all''' the plugins of a particular type.
+Diese Arten von Plugins werden verwendet, wenn es wünschenswert ist, alle Plugins eines bestimmten Typs zu laden.
-This mechanism is currently used in the following cases:
+Dieser Mechanismus wird derzeit in den folgenden Fällen verwendet:
-'''/OpenSim/Startup''' - application plugins (IApplicationPlugin). Loaded by OpenSimBase when OpenSimulator starts. The plugins are loaded using PluginLoader.
+'''/OpenSim/Startup''' - Anwendung Plugins (IApplicationPlugin). Wird von OpenSimBase geladen, wenn OpenSimulator gestartet wird. Die Plugins werden mit PluginLoader geladen.
-'''/OpenSim/RegionModules''' - region modules. Loaded by RegionModulesControllerPlugin, which is itself an application plugin. The plugins are loaded by calling AddinManager directly (not through PluginLoader).
+'''/OpenSim/RegionModules''' - Region-Module. Geladen von RegionModulesControllerPlugin, welches selbst ein Anwendungs-Plugin ist. Die Plugins werden durch direkten Aufruf von AddinManager geladen (nicht über PluginLoader).
-−
-'''/OpenSim/WindModule''' - wind models. Loaded by WindModule, which is itself a region module. The plugins are loaded by calling AddinManager directly.
 ==== Unused Extension Points ====

@@ Line 1: / Line 1: @@
-==Overview==
+==Überblick==
-OpenSimulator uses several mechanisms to enable dynamic configuration of functionality. This page describes these mechanisms.
+OpenSimulator verwendet verschiedene Mechanismen, um die dynamische Konfiguration von Funktionen zu ermöglichen. Diese Seite beschreibt diese Mechanismen.
 == Dynamic Plugins with Mono.Addins ==