On 20/10/06, Michael Bender <[EMAIL PROTECTED]> wrote:
Ludovic Rousseau wrote:
> Paul Klissner wrote:
>
>> I'd like to add SCARD_E_INVALID_DISPLAY to the list of err consts
>> in PCSC/pcsclite.h, and the text "Invalid $DISPLAY environment" to
>> pcsc_stringify_error(), but I am concerned that I might be
>> constrained by backward-compatibility issues.
>
> Can you describe the backward compatibility issues you are
> thinking about?
My question on this was who controls the error/status return code
name space of PC/SC-lite? Is that us, or is it the PC/SC standards
body?
The winscard error codes (SCARD_E_foobar names) are defined in
"Interoperability Specification for ICCs and Personal Computer
Systems, Part 5. ICC Resource Manager Definition" [1].
This list is not limited since Windows PC/SC defines some other codes:
#define SCARD_E_CANT_DISPOSE ((DWORD)0x8010000EL)
#define SCARD_E_CARD_UNSUPPORTED ((DWORD)0x8010001CL)
#define SCARD_E_DUPLICATE_READER ((DWORD)0x8010001BL)
#define SCARD_E_INVALID_ATR ((DWORD)0x80100015L)
#define SCARD_E_INVALID_TARGET ((DWORD)0x80100005L)
#define SCARD_E_NO_SERVICE ((DWORD)0x8010001DL)
#define SCARD_E_PCI_TOO_SMALL ((DWORD)0x80100019L)
#define SCARD_E_READER_UNSUPPORTED ((DWORD)0x8010001AL)
#define SCARD_E_SERVICE_STOPPED ((DWORD)0x8010001EL)
I guess pcsc-lite could also define some "non-documented" error codes.
I have no objection adding new error codes if they are reasonable and
used by at least one application.
I think you do not plan to port the Sun Ray server software on Windows? :-)
Bye,
[1] http://www.pcscworkgroup.com/specifications/files/pcsc5_v2.01.01.pdf
--
Dr. Ludovic Rousseau
_______________________________________________
Muscle mailing list
Muscle@lists.musclecard.com
http://lists.drizzle.com/mailman/listinfo/muscle
