Hello, Not to sound defensive, but I think (by bias) that this client side architecture is good for writing fast plug-ins. If the plugin level is at the PKCS-11 layer which it might be as well there is too much overhead for just a smartcard and each card driver shares much of the same certificate managing code with other drivers.
The idea behind Musclecard is simple: One very simple API that works with any vendor JavaCard If one wants to write support for their card they can do it but it may not be trivial. You may have some unsupported features. I didn't want to jeopardize the simplicity of the API to make it easier to support legacy hardware. I feel the future is in programmable smartcards and the MuscleCard protocol can be implemented on any of these by making the interoperability layer on the card itself........ Dave *************************************************************** Unix Smart Card Developers - M.U.S.C.L.E. (Movement for the Use of Smart Cards in a Linux Environment) http://www.linuxnet.com/ To unsubscribe send an email to [EMAIL PROTECTED] with unsubscribe sclinux ***************************************************************
