A T=1 question from a friend (read below) makes me wonder this:
1) Is the T=1 nitpick (splitting long data etc.) really implemented
in MUSCLE yet?
2) At what level is/should this be implemented? (CT-api, IFD-handler,
higher levels?)
3) Is there any source available that can be learned from or reused (GPL)?
Thanks
Morten
>For the ISO7816 protocol T=1, the APDU:s (=commands/responses) from the
>application have to be mapped onto TPDU:s (transport level). This involves
>framing by prologue/epilogue fields, splitting into blocks, chaining of
>these blocks etc. In the Linux PC/SC system, where is this done? In the
>IFD-handler or in any component above it?
>
***************************************************************
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
***************************************************************
