Our upcoming OmniKey RFID driver is going to support it! Mit freundlichen Grüßen Best regards,
Philipp Eichinger OMNIKEY GmbH Ferihumerstrasse 13 A-4040 Linz Austria Tel +43 (0) 732 / 602220 - 37 Fax +43 (0) 732 / 602220 - 15 E-Mail [EMAIL PROTECTED] Web www.aaitg.com "Ludovic Rousseau" <[EMAIL PROTECTED]> Gesendet von: [EMAIL PROTECTED] 11.10.2007 11:27 Bitte antworten an MUSCLE <[email protected]> An MUSCLE <[email protected]> Kopie Thema Re: [Muscle] Serial number problems! 2007/10/11, Martin Paljak <[EMAIL PROTECTED]>: > > On 11.10.2007, at 11:31, Ludovic Rousseau wrote: > > >> We are in favour of the second option, also I don't see the point > >> in adding > >> the serial number to the readername, while an application can also > >> retrieve > >> it via SCardGetAttrib(). > > > > Good point. > > What do other think about that? > > The reasoning to add the serial was to make a difference between two > same readers behind the same machine. As the reader selection works > with names in PCSC the application could get the wrong reader on a > second connect. At least the reasoning that was made when the feature > was added made a lot sense to me. Yes, I know why the reader serial number was added. Do you think it is still needed now that the application can get the reader serial number using SCardGetAttrib()? I don't think I will revert the default behavior (include the reader serial number in the PC/SC reader name) because: - the addition is made by pcsc-lite itself - SCardGetAttrib() will only provide the serial number if the driver support this feature. And I know no driver that can do that. Philipp, does the SCM proprietary driver support SCardGetAttrib() to get the reader serial number? bye -- Dr. Ludovic Rousseau _______________________________________________ Muscle mailing list [email protected] http://lists.drizzle.com/mailman/listinfo/muscle ------------------------------------------------------------ Meet us at: Intergraf, October 10-12, Nice, Booth 98 CARTES & IDentification, November 13-15, Paris, Booth 3F002 2nd Asia Pacific Transport Revenue Collection Discussion Forum, 24-25 October 2007, Taipei/Taiwan Confidential Notice: This communication may contain information that is proprietary, privileged or confidential or otherwise legally exempt from disclosure. The information contained in this email is intended solely for the addressee. Access to this email by anyone else or any unauthorized review, use, disclosure or distribution is unauthorized and prohibited. If you are not the named addressee indicated in this message (or responsible for delivery of the message to such person), you are not authorized to read, print, retain, copy or disseminate this message or any part of it. If you have received this message in error, please notify the sender immediately by fax or e-mail and delete and destroy all copies of the message. If you are the intended recipient but do not wish to receive communications through this medium, please advise the sender immediately. The views expressed in this email are not necessarily the views of OMNIKEY. The company, its directors, officers or employees make no representation or accept any liability for its accuracy or completeness unless expressly stated to the contrary.
_______________________________________________ Muscle mailing list [email protected] http://lists.drizzle.com/mailman/listinfo/muscle
