[15985] in Kerberos_V5_Development
Re: Plugin project proposal
daemon@ATHENA.MIT.EDU (Zhanna Tsitkova)
Thu Jul 15 14:25:31 2010
Message-Id: <A69DE956-8C53-42C9-AD42-1F54C352E720@mit.edu>
From: Zhanna Tsitkova <tsitkova@mit.edu>
To: Russ Allbery <rra@stanford.edu>
In-Reply-To: <87hbk0vf9c.fsf@windlord.stanford.edu>
Mime-Version: 1.0 (Apple Message framework v930.3)
Date: Thu, 15 Jul 2010 14:25:25 -0400
Cc: krbdev@mit.edu
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: krbdev-bounces@mit.edu
On Jul 15, 2010, at 1:14 PM, Russ Allbery wrote:
>>
>> 2. 2. It was suggested to use hash tables for the plugin
>> interfaces in
>> lieu of C structures. This would provide better plugin impl. version
>> control and interface extensibility.
>
> I'm not sure what you mean by hash tables here.
Suppose we have defined an interface for plugin_A.
At later time one may want to extend the interface of this plugin.
Now, can these two versions coexist? Yes, and one of the possible
solutions is to implement v-tables as hashes.
In this case the interface consumer can check for the availability of
the new method by querying the hash-table. If "new method" is not
implemented, it returns null pointer. And one can decide how to
proceed further.
_______________________________________________
krbdev mailing list krbdev@mit.edu
https://mailman.mit.edu/mailman/listinfo/krbdev
