[16028] in Kerberos_V5_Development
Re: Alternative proposal (was Plugin project proposal)
daemon@ATHENA.MIT.EDU (Jeffrey Hutzelman)
Sun Aug 1 21:26:26 2010
Date: Sun, 01 Aug 2010 21:26:20 -0400
From: Jeffrey Hutzelman <jhutz@cmu.edu>
To: Nicolas Williams <Nicolas.Williams@oracle.com>, krbdev@mit.edu
Message-ID: <7670D6A7C0B1B3E824BA2F8F@atlantis.pc.cs.cmu.edu>
In-Reply-To: <20100721174440.GF23748@oracle.com>
MIME-Version: 1.0
Content-Disposition: inline
Cc: jhutz@cmu.edu
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: krbdev-bounces@mit.edu
--On Wednesday, July 21, 2010 12:44:40 PM -0500 Nicolas Williams
<Nicolas.Williams@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
_______________________________________________
krbdev mailing list krbdev@mit.edu
https://mailman.mit.edu/mailman/listinfo/krbdev
