Hello,
2012/6/14 Umberto Rustichelli aka Ubi <[email protected]>:
> Apparently, by changing the version of the smart card module (it's a binary,
> not open source) the number of threads got drastically reduced and I could
> at least pass a first test.
>
> Questions now become:
>
> 1 - (curiosity still there, see questions in previous post):
> what is the exact meaning of PCSCLITE_MAX_THREADS?
This is no more used in recent version of pcsc-lite.
This has been removed from the source code in revision r4405 in September 2009.
> 2 - can I actually reduce the number of threads spawned by
> (each occurrence of) an application (a smart card module)
> by tweaking the PCSCD headers?
> I know that the threads are pcscd-related, so... is it
> possible that the module really needs them?
Each call to SCardEstablishContext() should create a pcscd thread.
If the application do not call the corresponding SCardReleaseContext()
then you have a problem.
You can't fix an application bug by changing a pcscd header.
> 3 - If so, how? Again... would my best guess be
> PCSCLITE_MAX_APPLICATION_CONTEXTS or is it
> PCSCLITE_MAX_APPLICATION_CONTEXT_CHANNELS?
According to README_INTERNALS.txt [1] (very outdated):
Maximum contexts by application
PCSCLITE_MAX_APPLICATION_CONTEXTS
Maximum channels on a reader context
PCSCLITE_MAX_READER_CONTEXT_CHANNELS
These two defines have also been removed from the source code some time ago.
You still do not want to upgrade pcsc-lite?
Bye
[1]
http://anonscm.debian.org/viewvc/pcsclite/trunk/PCSC/src/README_INTERNALS.txt?view=markup
--
Dr. Ludovic Rousseau
_______________________________________________
Muscle mailing list
[email protected]
http://lists.drizzle.com/mailman/listinfo/muscle
