Re: direct usage of socket file descriptor

2011-05-08 Thread Anton Vodonosov
Sorry, I posted it to the wrong list by mistate. 08.05.2011, 02:30, "Anton Vodonosov" : > Hello. > > Is it safe to retrieve a socket handle like this: > > (ccl::ioblock-device (ccl::stream-ioblock socket t)) > > and then perform some IO on it directly (in fore

direct usage of socket file descriptor

2011-05-08 Thread Anton Vodonosov
Hello. Is it safe to retrieve a socket handle like this:  (ccl::ioblock-device (ccl::stream-ioblock socket t)) and then perform some IO on it directly (in foreign code). Can this lead to any problems (like the Windows crush we are discussing in the ccl-devel)? Best regards,- Anton _

Re: does OpenSSL call locking-callback/thread-id-callback from any internal threads?

2011-04-11 Thread Anton Vodonosov
Thank you for the reply. 11.04.2011, 07:18, "David Schwartz" : > On 4/10/2011 3:03 PM, Anton Vodonosov wrote: > >>  The question: if I provide locking_callback, will it be called only from >> the threads where I invoke OpenSSL functions, >>  or OpenSSL may

does OpenSSL call locking-callback/thread-id-callback from any internal threads?

2011-04-10 Thread Anton Vodonosov
Hello. The question: if I provide locking_callback, will it be called only from the threads where I invoke OpenSSL functions, or OpenSSL may call it from some private/internal threads not created by me? I assume OpenSSL does not invoke the callback from any "not-mine" threads, because the docum