Paul wrote: > When it's best to use a TSslDynamicLock or TSslStaticLock ?
I used TSslStaticLock. TSslDynamicLock is untested and might leak memory if property Enabled was set to False while any _dynamically allocated lock-objects still exist, however I think that does not happen yet since OpenSSL does not seem to call those callbacks yet (just found one call to CRYPTO_get_new_dynlockid()in OpenSSL's engine source code which is not implemented by ICS). Although http://www.openssl.org/docs/crypto/threads.html describes it, even the mentioned example crypto/threads/mttest.c does not seem to use the dynlock API. BTW: If one only use OpenSSL functions and SSL components from one thread context at the same time no locking is required. -- Arno -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
