ooops,
I should read the OCF mails in the future more carefully.
I'm very sorry about that and I have to take your advise silently.
You are totaly right, in your following sentence the thinks were very
clear
described:
> When CardTerminal.internalSendAPDU() is called and a CommandAPDU must be
> mapped onto
> more than one TPDU this should be done in the terminal.
Please excuse my awful mistake.
Unfortunaly I'will not become rich now ;-), but however the decission to
encapsulate the protocol behaviour in the Terminal Service is obvious
the right one.
regards
Thomas
[EMAIL PROTECTED] wrote:
>
> Thomas,
>
> perhaps you misunderstood the term "CardTerminal". In OCF, the term
> "CardTerminal" refers to a class that encapsulates physical card terminals.
> Thus "handling T=0 in the CardTerminal" means that the client (in the OO
> sense) of a CardTerminal object does not need to handle T=0. T=0 handling
> must either be handled by the firmware of the physical card terminal or by
> the CardTerminal class that encapsulates the physical card terminal.
>
> This means that no card terminal hardware/firmware needs to be changed. If
> the physical card terminal doesn't handle T=0, it is still possible to
> handle it in the CardTerminal class encapsulating that physical card
> terminal.
>
> Best Regards,
>
> Thomas
>
> Thomas Schaeck
> IBM Pervasive Computing Division - Smart Card Solutions
> E-mail: [EMAIL PROTECTED] Tel.: ++49-7031-16-3479 Fax.:
> ++49-7031-16-4888
> Address: IBM Deutschland Entwicklung GmbH, Schoenaicher Str. 220, 71032
> Boeblingen, Germany
Visit the OpenCard Framework's WWW site at http://www.opencard.org/ for
access to documentation, code, presentations, and OCF announcements.
-----------------------------------------------------------------------------
To unsubscribe from the OCF Mailing list, send a mail to
"[EMAIL PROTECTED]" with the word "unsubscribe" in the BODY of the
message.
