>> Under PKCS#11 the only way to do this is to have one thread per crypto
>> operation. There was a parallel session interface in PKCS#11 at one
>> point but it is now been removed. The problem is not that PKCS#11
>> prevents threads just that it forces you to use them if you want to run
>> several crypto operations in parallel.
>
>No it does not. You simply attach multiple applications to a single
>token.
>An application in this context means that you have seperate process. If
>the token does some magic shared-mem or pipe stuff or similar, it has to
>hide this from the application. How Objects are visible between
>applications
>is described in the standard.
Um, this is definitely not the case everywhere. Operations that at least
*some* tokens perform can block, and have a relatively high period of latency
from submission to return. Multiprocess/multithread is definitely not the
only answer to dealing with this problem.
I don't understand what you're talking about in terms of shared-mem or pipes.
--Chris
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
