2012/6/7 Sébastien Lorquet <[email protected]>: > do you really need the "contactless" part of the information? > > if I had to do that, I would proceed in 2 steps > > -find readers that contain a card (already doable) > -send a specific command that is recognized by the card application, > typically it will be a select with an AID > -same idea is usable to find the reader that contains the sam. > > and that's all, you do not have contacts or radio waves in the equation. > > what about that?
I would also suggest something like that. For the autoconfiguration you can ask the user to "insert" a card into the reader the user wants to use. Then the application scans all the readers to find the one with the (new) card and stores the reader name in his configuration. For example, if you have 2 contactless readers you will not know which one is used to the user card and which one is used for the officer card. You will need the help of the user the first time you setup the application. On the other hand it is possible to propose something to the PC/SC workgroup. If I am correct you need a service to know what are the specificity of a reader. It could be something from the (non exhaustive) list: - contact - T=0 - T=1 - contactless - type A - type B - type C - other? - communication speeds ? - biometric ? It will be difficult (and time consuming) to setup the list of all possible features within the PC/SC workgroup. I do not plan to get any results before 5 years :-) Regards, -- Dr. Ludovic Rousseau _______________________________________________ Muscle mailing list [email protected] http://lists.drizzle.com/mailman/listinfo/muscle
