Alternative proposal (was Plugin project proposal)
Jeffrey Hutzelman
jhutz at cmu.edu
Sun Aug 1 21:26:20 EDT 2010
--On Wednesday, July 21, 2010 12:44:40 PM -0500 Nicolas Williams
<Nicolas.Williams at oracle.com> wrote:
> - The framework itself provides just a few utility functions and
> macros, as well as the build tools to generate header files from
> plugin type definitions:
>
> - a function to load a given plugin of a given plugin type
> - a function to load all plugins of a given plugin type
> - a macro to obtain the function pointer for a given entry point in
> a given plugin of a given plugin type
> - a macro to call a given entry point in a given plugin of a given
> plugin type
I think you need some mechanism to enumerate all of the (loaded/enabled)
plugins of a given type, possibly with a wrapper for calling the same entry
point in each plugin until some appropriate result is returned. For
example, I'd expect to need such interfaces in building the open-by-name
interfaces for keytabs and ccaches, where one would have to either give
each plugin a chance to handle a name or else have built a mapping from
schemes to plugin handles.
-- Jeff
More information about the krbdev
mailing list