Hi, >The source build was tuned for protocol development, rather than operations, >simplifying and eliminating many build options. Which is the protocol level involved?
> Aspects of the event-handling drivers for�PCSC API were changed, to allow linking > and use of�TLP-224 winscard.dll implementations - which are "less feature-rich" than > those > from Microsoft and PCSC-lite which assume a reliable, high-bandwidth environment for > card events. What do you call TLP-224 winscard.dll? I thank that TLP is a transport protocol between the reader and the host. Why is it "less feature-rich" than PC/SC from M$ and than PC/SC Lite? > Ill send the raw material to anyone who will try building it and comment back. Send it to me in order I look your works. > 1. how could the build be re-integrated with the official muscle source > distributions, so build support for Win32 using MSVC becomes more generalized? We think to do 2 packages in the future: one for PC/SC Lite and one for the Muscle library. It may be easier to re-integrate your work. Mainly this separation will allow an easier understanding of the framework to the developers and users > 2. should we even maintain a publicly available win32 build for the muscle > framework, and if we do, should it use the MinGW toolchain, rather than MSVC? I prefer the solution with MinGW rather than MSVC because MinGW is free. Regards, Damien Sauveron ------------------------------------------------- This mail sent through IMP: http://horde.org/imp/ _______________________________________________ Muscle mailing list [EMAIL PROTECTED] http://lists.musclecard.com/mailman/listinfo/muscle
