2011/10/18 Kalev Lember <[email protected]>: > On 10/18/2011 10:03 AM, Ludovic Rousseau wrote: >> 2011/10/17 Kalev Lember <[email protected]>: >>> I think in the long run we'll instead want to have >>> 'WantedBy=smartcard.target' and configure it for hardware activation. >>> But I haven't yet looked into how it works so I don't know the details. >> >> Is the idea to start pcscd when a smart card reader is connected? >> Why do you want that? > > pcscd can be slow to start like you write above. If pcscd is set to > start on-demand, first call to SCardEstablishContext() could possibly > delay client application for quite some time. > > Now, if pcscd was started when the hardware is connected, we would be > able to be get rid of the initial delay, and also possibly completely > avoid starting pcscd when there's no supported hardware. (Not sure if > that would work in practice, with e.g. serial readers.)
On my system the delay between pcscd start and the ATR is available is 458 ms (or half a second). I think 0.5 second is quiet fast compared to the time then used by the application to send APDU to the card. What is your limit for a slow start? Do you think 0.5 second is not fast enough? For my test I used a Gemalto GemPC Twin reader. Some other USB reader are far slower to start. I may add the boot time reader performances in the reader matrix one day. But that is a lot of work to get all the numbers. Thanks -- Dr. Ludovic Rousseau _______________________________________________ Muscle mailing list [email protected] http://lists.drizzle.com/mailman/listinfo/muscle
