in computer science everything is possible. But what is best for your users, ie easy to use still universal enough?
I don't like this towitoko code because it does things behind your back. When I send an APDU, I expect to know what goes to the card. if a driver does that, and another driver does not do that, then your card/software behaviour can depend on the reader! especially during software development I think it is useful to have a stable low level layer. In this thread, I described the standard pcsc behaviour, because I think this is the best way to implement the software given the non-layered nature of T=0. And I'm convinced that proper Le handling is important and must be managed by the application. From my experience in my company, this is the only way I know to stay compatible with all cards on the market, including old cards and new cards, contact cards and contactless cards. At least that's my opinion, and I agree with myself :-) Regards, Sebastien On Thu, Jul 8, 2010 at 10:24 AM, Wayne Wang <[email protected]> wrote: > hi Sebastein, > > here is code section for towitoko > http://towitoko.sourcearchive.com/documentation/2.0.7-8/protocol__t0_8c-source.html > > It handles the APDU directly in the driver. > Any comment :) > > B.R. > Wayne > > -----Original Message----- > From: [email protected] > [mailto:[email protected]] On Behalf Of Sébastien Lorquet > Sent: Thursday, July 08, 2010 14:34 > To: MUSCLE > Subject: Re: [Muscle] T=0 Case 2 response length > > One more thing: > >> >> It is so weird to let the dependency exist from bottom to top. > > In fact, I do not think that's not a dependency. That just means that T=0 is > unable to transfer a case 4 command at once. > The fact that the direction of the transfer MUST be known prior to the > transfer also implies that you must know the response length. > > If the response length is not what the card expected, there is no way to make > the host and the card agree on the action to be taken. So instead of relying > on timeouts, the designers preferred to be sure of the transfer length. So if > the transfer length is not OK for BOTH the host and the card, the latter one > sends 61 or 6C as SW2, so that the host can agree with the card, or abort the > transfer. > > Sebastien > _______________________________________________ > Muscle mailing list > [email protected] > http://lists.drizzle.com/mailman/listinfo/muscle > > > _______________________________________________ > Muscle mailing list > [email protected] > http://lists.drizzle.com/mailman/listinfo/muscle > _______________________________________________ Muscle mailing list [email protected] http://lists.drizzle.com/mailman/listinfo/muscle
