> Most of the drivers pass the 61 XX back to the application to handle. I
> think it is bad practice to handle this in the driver since it is a card
> specific ISO function.
GET RESPONSE is a transport level command. It should therefore be invisible
for the application. The problem arises if you write applications that work
with cards that support either T=0 or T=1 transport via PPS. If the reader
hardware is capable of doing either T=0 or T=1, then the application always
would need to know what protocol is used. If it is T=0, then it would need
to send GET RESPONSE, if it is T=1 then it would not send a GET RESPONSE.
ISO7816-4 was specifically rewritten at some point in time to eliminate
dependencies on T=0. ISO7816-4 now defines command and response APDU in the
first part and defines the mapping of these APDUs onto T=0 or T=1 transport
in the annex.
Andreas
***************************************************************
Linux Smart Card Developers - M.U.S.C.L.E.
(Movement for the Use of Smart Cards in a Linux Environment)
http://www.linuxnet.com/smartcard/index.html
***************************************************************
