To generate a library suitable for multithreaded use, the malloc and free implementations must be the same as the ones used by the rest of the program. (That's the number one issue.) A second issue is that certain data structures must be wrapped in mutexes (linked lists, as only one example). These need initialization of the functions to use when the library is called.
On systems with pthreads support, it will use pthreads. On systems with other thread-type support, it will use that system. On Windows, it will enforce that the multithreaded libraries are referenced, as opposed to the singlethreaded libraries. -Kyle H On 8/21/06, Ryan Shon <[EMAIL PROTECTED]> wrote:
I am trying to decide whether building OpenSSL with "threads" option is appropriate or not for my particular situation. The Configure script says that the option "tr[ies] to create a library that is suitable for multithreaded applications." How exactly are the libraries created to be suitable for multithreading? Is it related to how dynamic linking works for a multithreaded app? Does it enable SSL protocols to increase efficiency by splitting up processing among parallel threads? Does it involve kernel-specific code to handle the multi-threading? Thank you for your help ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List openssl-users@openssl.org Automated List Manager [EMAIL PROTECTED]
-- -Kyle H ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List openssl-users@openssl.org Automated List Manager [EMAIL PROTECTED]
