Hi, I've recently started looking at OpenSSL programming API and I'm a bit confused about thread locking funtions:
1. Static VS Dynamic locking callbacks Why have both? Does OpenSSL use dynamic callbacks? Can I omit static callbacks and only use dynamic, or maybe static callbacks are mandatory when using threads? How does OpenSSL choose a maximum number returned by CRYPTO_num_locks()? Does this number limit overall concurrency in OpenSSL? Is there a way to increase it in case I have to work with a large number of threads? 2. Rationale for callbacks? Pushing some of the responsibility for locking OpenSSL internal structures to application developers seems a bit lame. Why not get rid of locking callbacks and have OpenSSL handle it transparently inside the library? This promotes the idea of abstract data types and encapsulation and avoids the whole mess of static/dynamic callbacks. ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List openssl-users@openssl.org Automated List Manager majord...@openssl.org
