Hi Carl, First, I want to say that I know anything about the code Muscle PKCS#11.
> I was disappointed to discover that the Muscle PKCS11 libraries don't > support what I would consider to be some pretty basic features listed > in the PKCS11 spec. For example, the C_WaitForSlotEvent is the only > way (other than the inefficient solution of constant polling) to be > notified of changes in the slot state (i.e. when a token is inserted > or removed from the reader). > > The funny thing is, there are extension functions that provide this > exact functionality (async_StartSlotWatcher et. al). It seems strange > that the author went to the trouble of adding the feature but he > didn't add a standards-compliant way to use it. I don't know if it may interest you but there was a thread [1, 2, 3] on a Muscle callback 2 month ago and I have looked in the code of Muscle PKCS#11 that the function "async_StartSlotWatcher" uses this callback. I hope it will help you. Feel free to submit patch on [4]. [1] http://archives.neohapsis.com/archives/dev/muscle/2004-q2/0169.html [2] http://archives.neohapsis.com/archives/dev/muscle/2004-q2/0170.html [3] http://archives.neohapsis.com/archives/dev/muscle/2004-q2/0172.html [4] http://alioth.debian.org/projects/muscleapps/ Regards, -- Damien Sauveron ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program. _______________________________________________ Muscle mailing list [EMAIL PROTECTED] http://lists.drizzle.com/mailman/listinfo/muscle
