> bear> In contrast, with a plug-in the framework itself acts as the loader, > bear> and it must detect mising symbols in older shared libraries. Depending > bear> on the way it's hooked, it either has to resolve each symbol individually > bear> or a single structure and then check the version number. > > The way we've done it with the ENGINE framework is that the engine > itself has to tell libcrypto exactly what functionality it offers.
That makes sense with ENGINE since there's so much variability in what can be offered by the engine. If the hardware doesn't support a particular cipher or type of key, that's the end of it. But any DB plugin can be required to support every function in the API at the time it is loaded. It may not be *fast*, but it should be supported. (Modulo explicitly optional functions such as load() and unload()). Knowing the version should be sufficient to know which functions are present. ______________________________________________________________________ OpenSSL Project http://www.openssl.org Development Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
