Hey,
>Might it be a Win32 conflicting-runtimes problem? If all components of your
>application, including the DLLs you're using (such as OpenSSL) that rely on
>the C runtime, don't use the same incarnation of the MS C runtime, you can
>run into a variety of synchronization and memory allocation problems.
Not sure about Cory, but in my case this is not trouble: I built the SSL
libraries with the same compiler and linker as I use for my project -
everybody's using the same DLLs and libraries - multithreaded. Anyway, if
I can guarantee that while an SSL function is in use another will not be
called until the first has returned, it shouldn't really matter to SSL
whether I'm using threads or not... right? The only thing important then
is the order in which I am calling the functions.
Q
______________________________________________________________________
OpenSSL Project http://www.openssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
