Hello, 2009/2/3 Martin Preuss <aquaman...@gmx.de>: > 1) with pcscd all readers are always *on*. As soon as a reader is connected it > is started and polled for card insertion and removal even when there is no > client. I would very much like the pcscd to only power up a reader if there > is at least one client. This also serves as a nice visual control (on my > system I have reason to be suspicious if a reader suddenly starts up unless I > actually started a client myself).
pcscd does not "power up [the] reader" but power up the _card_ even if no application is using this reader/card. Is that what you wanted to write? That is point 2 on the pcsc-lite TODO list. Or do you know a way to power on and off a reader? > 2) it would be nice to have non-blocking access, especially when working with > a GUI. I know that this could be implemented in the application by using > threads, but it would be much nicer to have this in the API. You want non-blocking PC/SC functions? A non-blocking SCardTransmit for example? This would be an evolution of PC/SC and should be defined by the PC/SC workgroup and implemented by the other PC/SC "vendors" (Microsoft, Apple, Sun). Maybe you can write a library between PC/SC and your application to provide an asynchronous PC/SC API. But that is yet another smart card framework and we try to limit them. > 3) I like the idea of having a driver running inside its own process (as Alon > proposes) as opposed to using threads. That way a problem of a driver doesn't > affect the daemon. This is especially important to me when proprietary > drivers are used: I feel much safer if such a driver doesn't have control > over the whole daemon process. Good point. But my target is not to ease the use of proprietary drivers. So it will be a very low priority on my list. > While the second point will probably never be implemented unless it becomes > part of the PC/SC specs (which I doubt) I believe the first point should be > considered, especially when it comes to laptops. I agree. One important information would be to know the consumption of a reader with a card powered up and the consumption of the same reader with the card NOT powered up. I have no idea of the possible gain here. It may be far much efficient to unplug the reader. Regards, -- Dr. Ludovic Rousseau _______________________________________________ opensc-devel mailing list opensc-devel@lists.opensc-project.org http://www.opensc-project.org/mailman/listinfo/opensc-devel
