Correction to what I said before: I had forgotten this, but it is also possible for the calling app to specify the flag CKF_LIBRARY_CANT_CREATE_OS_THREADS, to which Cryptoki has the option of responding with CKR_NEED_TO_CREATE_THREADS. So the library appears to be functioning properly. When implementing C_WaitForSlotEvent, I plan to return a CKR_GENERAL_ERROR if the function is called in non-threaded mode.
Carl On Wed, 14 Jul 2004 15:55:31 -0700, Carl Youngblood <[EMAIL PROTECTED]> wrote: > mattered because the only functions supported are synchronous. The > PKCS11 spec says that the threading flags in C_Initialize are used to > indicate whether or not "an application will be accessing Cryptoki > through multiple threads simultaneously," not whether or not Cryptoki > can use multiple threads to handle its own operations. Cryptoki would > have to use multiple threads to support the C_WaitForSlotEvent > function. _______________________________________________ Muscle mailing list [EMAIL PROTECTED] http://lists.drizzle.com/mailman/listinfo/muscle
