You're right! We simply did not need such beast for ourselves, but it should be easy to build one as smartcardio is really a subset. I will have a look on this, after i managed to publish what we already have.
Maybe someone out there that can point out the *exact* PCSC semantics for the smartcardio default implementation (wrt lifecycle/connection/transaction) - i'd rather don't want to dig in this source code. On Fri, Jul 5, 2013 at 3:43 PM, Martin Paljak <[email protected]>wrote: > On Fri, Jul 5, 2013 at 2:32 PM, Michael Traut <[email protected]> > wrote: > > We'd like to donate this lib if anybody is interested... > ... > > > For some, the downside may be that we do NOT plug in smartcardio and have > > different abstraction for terminal/card/connection. The "card" > abstraction > > (while not required, but really recommended) is quite strict and on the > > exact opposite of smartcardio. Every card terminal and every card > connection > > comes with its own context... > > But maybe having a compatibility layer (with some gotchas) would make > it relatively easy (in terms of refactoring complexity) to have > code-style compatibility with javax.smartcardio? > > _______________________________________________ > Muscle mailing list > [email protected] > http://lists.musclecard.com/mailman/listinfo/muscle_lists.musclecard.com >
_______________________________________________ Muscle mailing list [email protected] http://lists.musclecard.com/mailman/listinfo/muscle_lists.musclecard.com
