Hi I also agree with that opinion. In my company we have highly complex SAMs that can handle multiple *long* transactions (up to around one minute) and it would be a problem if the card was powered down in the process.
Autopoweroff shall be an optional, non default activated feature. btw I agree it's useful in some cases where power consumption is an issue. Sebastien PS: background threads in a *card* ... how awful x_x ! On Sun, Oct 24, 2010 at 3:19 PM, s.ferey <[email protected]> wrote: > Hello Ludovic, All, > > I see at least 3 issues with auto power-off: > > - under Windows (may be also on Linux) the smardcard withdrawal can lock > the station; a power off of the cad will result in unexpected log-out. > > - a SSO solution may/should rely on a backgroung process that controls all > smartcard requests, but still one can design a solution based on an "short > life time" application to gain card access (user verification, on-card > context establishment) and then small clients for signature, data storage, > etc, requests - such clients will expect the card to keep its context. > > - JavaCard 3.0 introduces "distributed services", such a card can have > running background threads w/o applications actually connected - the card > behaves as a server and thus must keep a context alive. > > Regards, > Sylvain. > > > Le 24/10/2010 11:56, Ludovic Rousseau a écrit : > > >> Hello, >> >> I just implemented a new feature in pcsc-lite: card auto power on and off >> I describe the mechanism in an article [1] on my blog. >> >> Play with the new code, break it and report bugs :-) >> >> Bye >> >> [1] >> http://ludovicrousseau.blogspot.com/2010/10/card-auto-power-on-and-off.html >> >> > > > _______________________________________________ > Muscle mailing list > [email protected] > http://lists.drizzle.com/mailman/listinfo/muscle >
_______________________________________________ Muscle mailing list [email protected] http://lists.drizzle.com/mailman/listinfo/muscle
