Password sync plugin, and questions about plugin criticality

[Ken Hornstein]

>>I don't think I follow this; how exactly is this supposed to work?
>>Specifically, I don't understand what kapi_pblock_* is doing.
>
>OK, perhaps an example was the wrong approach. What I was trying
>to convey was that can be useful for each entry point to take a
>single (or well defined number of) argument(s).
>
>One argument would be an opaque "parameter block" or handle; the
>SPI would provide appropriate accessor functions.
>
>That way both the API and ABI can be maintained as the interface
>is extended. It can also make it easier to generalize the SPI
>layer for different sorts of plugins.

Ah, okay, I understand now.  MIT does that a different way (their plug-in
interface does versioning), but they already have functions that take
varying number of arguments, so I don't think that's a concern.

--Ken