Thanks for your solution. But if using shared memory, the shared memory address attached in the [Request Handler] and [Request Parser] may be different, the SSL object will not usable in both process.
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Goetz Babin-Ebell Sent: Tuesday, May 10, 2005 4:17 AM To: openssl-users@openssl.org Subject: Re: How to pass SSL connection/object from one process to another? lewislyk wrote: > Sorry, I do not have the idea what you mean? > What is the OpenSSL memory handler? If I was unclear: OpenSSL doesn't call the memory handling functions (malloc, realloc, free) direct. It uses memory allocate functions (OPENSSL_malloc(), OPENSSL_realloc() and OPENSSL_free()) With CRYPTO_set_mem_functions() you can set the internally used memory handling functions and become OpenSSLs master do decide if and where new memory will be allocated... > But you can overwrite the OpenSSL memory handler. > Create an new one that has an (thread specific) flag > to indicate if the data should reside in the shared memory. > Now every time you do SSL data, you set the flag and > the SSL data will be allocated in the shared memory... Bye Goetz -- DMCA: The greed of the few outweighs the freedom of the many ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List openssl-users@openssl.org Automated List Manager [EMAIL PROTECTED]
