Plugin project proposal

[Zhanna Tsitkova]

Well, it is more about lower level design and may not be necessary in the first plugin framework implementation , but one approach comes to mind:

Based on configuration one can build dependency matrix.
Its rows and columns represent all desired plugin  implementations, say, A B C D. Now, if A depends on B the location (A,B) gets the value 1, otherwise 0. And so on. The next step is to create a priority vector based on this matrix and pass it to the initializer.

Just an idea.

Thanks,
Zhanna
________________________________________
From: Nicolas Williams [Nicolas.Williams at oracle.com]
Sent: Thursday, July 15, 2010 1:43 PM
To: Zhanna Tsitkova
Cc: krbdev at mit.edu
Subject: Re: Plugin project proposal

On Thu, Jul 15, 2010 at 12:59:01PM -0400, Zhanna Tsitkova wrote:


> 4.     4. Notion of the plugin properties configuration attribute.  It
> was introduced in the project to allow the administrator to pass some
> additional information to the plugin manager. For example, to be
> initialized, Plugin_A requires Plugin_B to be initialized first.
> Plugin manager now would arrange the proper init order or pass the
> desired parameters to the plugin module.

How is init order established?


Nico
--