RES: RES: Parallel Process with readers - pcsc-lite
MURILO COSTA <[email protected]>
| Newsgroups | gmane.comp.lib.muscle |
|---|---|
| Message-ID | <6619ABDE51567D4C82080B841A45444A7C6CD2BC@CH1PRD0210MB359.namprd02.prod.outlook.com> |
Hello,
$ lsusb
Bus 002 Device 031: ID 046a:002d Cherry GmbH SmartTerminal XX44
Bus 002 Device 003: ID 0a5c:5801 Broadcom Corp. BCM5880 Secure Applications....
$ lsusb -v | grep bMaxCCIDBusySlots
bMaxCCIDBusySlots 1
bMaxCCIDBusySlots 1
Look like the readers are not the problem, anyway I'm testing it with pcsc-tools
About the possible Java limitation, I'll take a look, the code of Frank maybe can help
Regards,
Murilo
________________________________________
De: Muscle [[email protected]] em nome de Ludovic Rousseau [[email protected]]
Enviado: quarta-feira, 3 de julho de 2013 16:45
Para: MUSCLE
Assunto: Re: [Muscle] RES: Parallel Process with readers - pcsc-lite
2013/7/3 MURILO COSTA <[email protected]>:
> I thought that maybe can be a Java problem, do you know some software to do this kind of test (parallelism) ? I'll check if pcsc-tools can do that...
I guess it is a javax.smartcardio "limitation".
You need to create one context per reader using SCardEstablishContext.
I bet the Java wrapper creates only one context for all the readers.
In pcsc-lite the context is associated to a mutex. So all your
commands will block on the same mutex even if they use different
readers.
I don't know if is it easy or even possible to avoid this Java wrapper
"feature".
> Do you think that issue have some relationship with this Ludovic post:
> http://ludovicrousseau.blogspot.com.br/2013/06/ccid-descriptor-statistics_7148.html
No.
Bye
--
Dr. Ludovic Rousseau
_______________________________________________
Muscle mailing list
[email protected]
http://lists.musclecard.com/mailman/listinfo/muscle_lists.musclecard.com