Thanks, Kyle for the reply. Does anyone have a definitive answer for this one? It could be a massive amount of work for me to rewrite the code if I have to switch to using a single thread for read/write operations.
> -----Original Message----- > Mark: I don't know if the structure is managed in a way that allows > multiple threads running on multiple processors to reflect changes to > the structure state made by or on the others (such as with the > 'volatile' keyword). I also don't know if every function that > manipulates the SSL structure properly wraps the access with locks. > > It's probably best to go by the advice given in the FAQ, that SSL > objects should not be shared across threads. You might be able to > wrap your own accesses, but I don't know how the optimization done by > your compiler would affect it, and you might end up with > hard-to-diagnose bugs. ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List openssl-users@openssl.org Automated List Manager [EMAIL PROTECTED]
