My ENGINE uses DSO_load to open up our crypto hardware interface library, which is of course a dso, or a DLL under windows. I do use the DSO_FLAG_NAME_TRANSLATION bit to get OS portability. The DSO library is very nice for OS portability. But I have one question - is there any pass-through for versioning? I can see that external library versioning (such as libBlah.so.1.0) is a portability problem, because there are different OS styles, and some don't do it at all. If DSO_load can't track the library version, I will want to do it internally, by adding a 'get library version' method. We are slowly slouching toward release of our ENGINE, and it wouldn't do to only add the get_version method in version 2... ;-) Tom Biggs ______________________________________________________________________ OpenSSL Project http://www.openssl.org Development Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
