Hello,
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. This should happen above the reader abstraction
where the card abstraction layer occurs. BTW - has anyone done an OSI
like modeling for how a smartcard infrastructure should occur ?
Regards,
Dave
On Mon, 30 Jul 2001, Naomaru Itoi wrote:
> When a card returns 61.xx, it means that the card has xx byte to
> return to host.
>
> Does a smartcard reader driver handle this, usually? Does it
> automatically send get_response APDU and get the return data, or does
> it pass the status code 61.xx to the application?
>
> I am not trying to find out which the right way is. I am trying to
> find out how the actual reader drivers do it.
>
> Thank you.
>
> --
> Concentration .. Naomaru Itoi, coding @ home
> ***************************************************************
> 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
> ***************************************************************
>
***************************************************************
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
***************************************************************
