[Pcsclite-cvs-commit] r6362 - /trunk/PCSC/src/winscard_clnt.c

rousseau at users.alioth.debian.org rousseau at users.alioth.debian.org
Tue Jun 26 14:22:16 UTC 2012


Author: rousseau
Date: Tue Jun 26 14:22:15 2012
New Revision: 6362

URL: http://svn.debian.org/wsvn/pcsclite/?sc=1&rev=6362
Log:
With changes in revisions 6358 to 6361 it is now possible to use the
same SCARDCONTEXT in different threads (same as on Windows)

With one context per thread the locking was controlled by the daemon.
With the same context for 2 threads the locking is controlled (first) on
the client side since the 2 threads uses the same mutex.

Modified:
    trunk/PCSC/src/winscard_clnt.c

Modified: trunk/PCSC/src/winscard_clnt.c
URL: http://svn.debian.org/wsvn/pcsclite/trunk/PCSC/src/winscard_clnt.c?rev=6362&op=diff
==============================================================================
--- trunk/PCSC/src/winscard_clnt.c (original)
+++ trunk/PCSC/src/winscard_clnt.c Tue Jun 26 14:22:15 2012
@@ -68,12 +68,6 @@
  *    shared mode (like with \ref SCARD_SHARE_SHARED) and not in
  *    exclusive mode (like with \ref SCARD_SHARE_EXCLUSIVE) as on
  *    Windows.
- * -# SCardEstablishContext()
- *    @par
- *    Each thread of an application shall use its own \ref SCARDCONTEXT.
- *    SCardCancel() is the only exception to the rule.  On Windows the
- *    same \ref SCARDCONTEXT can be shared by different threads of same
- *    application.
  * -# SCardConnect() & SCardReconnect()
  *    @par
  *    pdwActiveProtocol is not set to \ref SCARD_PROTOCOL_UNDEFINED if




More information about the Pcsclite-cvs-commit mailing list