logo_kerberos.gif

Projects/Plugin support improvements

From K5Wiki
< Projects(Difference between revisions)
Jump to: navigation, search
(Motivation)
(Motivation & Requirements)
Line 2: Line 2:
 
==Motivation & Requirements ==
 
==Motivation & Requirements ==
   
We set up our goal on creating a framework that
+
There are a number of motivations behind the creation of the plugin architecture framework.
  +
Some of these include the following:
   
 
* Separates plugin interface from its implementation;
 
* Separates plugin interface from its implementation;
Line 10: Line 10:
 
* Provides uniform way to supply parameters for plugin configuration;
 
* Provides uniform way to supply parameters for plugin configuration;
 
* Allows one plugin implementation to use services provided by the other plugin implementations.
 
* Allows one plugin implementation to use services provided by the other plugin implementations.
  +
  +
From these items we have developed a more formal set of requirements
  +
covering the design and the implementation of the framework to
  +
support the plugins. These are as follows:

Revision as of 09:10, 21 July 2010

Motivation & Requirements

There are a number of motivations behind the creation of the plugin architecture framework. Some of these include the following:

  • Separates plugin interface from its implementation;
  • Provides simple and clear mechanism that facilitates additions of new plugin interfaces and their implementations(modules);
  • Handles both built-in and dynamic plugin modules;
  • Allows multiple implementation of the same plugin interface;
  • Provides uniform way to supply parameters for plugin configuration;
  • Allows one plugin implementation to use services provided by the other plugin implementations.

From these items we have developed a more formal set of requirements covering the design and the implementation of the framework to support the plugins. These are as follows:

Personal tools