Plugin project proposal

[Jeffrey Hutzelman]

--On Thursday, July 15, 2010 02:31:28 PM -0500 Nicolas Williams 
<Nicolas.Williams at oracle.com> wrote:

> On Thu, Jul 15, 2010 at 03:06:11PM -0400, Zhanna Tsitkova wrote:
>> On Jul 15, 2010, at 2:57 PM, Nicolas Williams wrote:
>> > What is used as a key to the table?
>>
>> Suppose we have the following v-table for plugin password quality:
>> /* PWD_QLTY API */
>> typedef struct {
>> int version;
>> char plugin_id[MAX_PL_NAME_LEN];
>> kadm5_ret_t (*pwd_qlty_init)(kadm5_server_handle_t);
>> void (*pwd_qlty_cleanup)();
>>  kadm5_ret_t (*pwd_qlty_check)(kadm5_server_handle_t, char*,int,
>> kadm5_policy_ent_t, krb5_principal);
>> } plugin_pwd_qlty;
>>
>> Then the key may be "pwd_qlty_check"
>
> I think this is still ridiculously complicated.
>
> It'd all be simpler with a dlsym() over v-table approach

Yes.  Yes it would.  After all, what's being described here is a 
reimplementation of symbol table lookup, again with no advantage I can see 
over use of dlsym().  But, I seem to recall we've had that argument already.