What you're proposing is good in that it reflects a very practical desire to avoid changing too much code, but it might not be the best solution. Why assume that both ATRs should be registered? Why not change the way PCSC-Lite determines if a new card has been inserted? (These are just long-term suggestions, not short-term fixes)
On Mon, 26 Jul 2004 15:50:16 -0500, David Corcoran <[EMAIL PROTECTED]> wrote: > Ultimately, the MuscleCard layer would have to have it's sanity checks > removed so that it does not care if the ATR changes during a card > lifecycle.... > Next, both ATR's would have to be registered with the bundle .... > I don't think pcsc-lite cares about the ATR changing but I could be > wrong .... > > Dave > > > > > On Jul 26, 2004, at 3:39 PM, Carl Youngblood wrote: > > > > > > ************************************************************************ > ***** > David Corcoran <[EMAIL PROTECTED]> > Identity Alliance [http://www.identityalliance.com] > Smart Cards, Biometrics, Training, Identity Management > ************************************************************************ > ***** > > _______________________________________________ Muscle mailing list [EMAIL PROTECTED] http://lists.drizzle.com/mailman/listinfo/muscle
