|
|
|
|
|
|
|
|
|
|
|
|
| home | help | back | first | fref | pref | prev | next | nref | lref | last | post |
From: Sam Hartman <hartmans@mit.edu> To: Tom Yu <tlyu@mit.edu> Date: Fri, 28 May 2010 13:19:43 -0400 In-Reply-To: <ldvvdabtz4o.fsf@cathode-dark-space.mit.edu> (Tom Yu's message of "Tue, 25 May 2010 18:06:31 -0400") Message-ID: <tslfx1cvt8w.fsf@mit.edu> MIME-Version: 1.0 Cc: krbdev@mit.edu Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: krbdev-bounces@mit.edu Like Nico, I have a reasonably strong preference for function-per-interface rather than vtables. The main reason is that it's easier to code the plugin and we want to optimize for simplicity of creating plugins. I've considered the arguments about how to handle version changes, and tend to agree with Nico. Vtables are nice if you want to consider static loading. I will note this is a departure from the approach we took for the preauth plugins and that was a concious decision, although I don't remember whether it was our decision or simply something we accepted when we accepted the code from RH. The authdata interface was explicitly modeled on the preauth interface. --Sam _______________________________________________ krbdev mailing list krbdev@mit.edu https://mailman.mit.edu/mailman/listinfo/krbdev
|
|
|
|
|
|
|
|
|
|
|
|
| home | help | back | first | fref | pref | prev | next | nref | lref | last | post |