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.
Oups Yes.. The solution for that would be a translator that knows the memory address of the old data in the old scope and the new scope. But then you would have to step though the whole SSL data and translate all pointers...
I think you should use a thread in the request parser process as frontend for the handler (doing the SSL stuff and passing the unencrypted data to a local socket).
Bye
Goetz
-- DMCA: The greed of the few outweighs the freedom of the many
smime.p7s
Description: S/MIME Cryptographic Signature
