Plugin project proposal
Nicolas.Williams at oracle.com
Thu Jul 15 17:35:55 EDT 2010
On Thu, Jul 15, 2010 at 05:33:18PM -0400, Zhanna Tsitkova wrote:
> Well, it is more about lower level design and may not be necessary in
> the first plugin framework implementation , but one approach comes to
> 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.
What component would build this matrix? Surely not the application.
That's a non-starter.
Keep things simple please. That's the point of a plugin framework. If
you can't keep things simple then give up on the plugin approach.
More information about the krbdev