Re: PCSC plans?

Hi,

On Friday 14 April 2006 01:31, Joachim Breitner wrote:
[...]
> with chipcardd1 I could access the pcscd daemon, which I need anyways,
> instead of the hardware directly. In chipcardd2, that support does not
> seem to be included, which means that I have to kill pcscd before using
> HBCI and start it afterwards, which is inconvenient. Are there any plans
> to re-enable pcscd support?
[...]

No, currently there aren't such plans. From my point of view it is more a 
problem of PC/SC not releasing readers while there is no PC/SC client who 
needs to access them.

Libchipcard-1 did the same, it just grabbed any reader it could get its hands 
on (as PC/SC does), but I didn't think that this was the right way to do it.

Therefore Libchipcard-2 is much less aggressive: It only grabs any readers if 
(and only if) a libchipcard-2-client wants to access them, leaving the 
readers available to other programs (like Moneyplex etc) when there is no 
libchipcard2-client. It keeps track of plugged/unplugged readers all the 
time, but it doesn't access them until there is need to do so.

Libchipcard2 provides ressource management, as PC/SC does (it even uses PC/SC 
drivers directly). So writing a Libchipcard2 interface to PC/SC would 
introduce an additional ressource manager layer which doesn't make too much 
sense.

It wouldn't be too hard to write such a driver, though, given the simple 
structure of Libchipcard2 drivers.


Regards
Martin
-- 
"Things are only impossible until they're not"

AqBanking - http://www.aqbanking.de/
LibChipcard - http://www.libchipcard.de/


-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642