--On Monday, February 02, 2009 07:38:23 PM +0100 Andreas Jellinghaus 
<[email protected]> wrote:

> but keeping openct around with or without ccid
> driver, or having some other drivers around
> to implement non-ccid drivers all ends up with
> the same result: lots of common functionality in
> several places.

The solution to this, I think, is some kind of library containing common 
code.  That could be part of pcscd, or a separate library that drivers link 
against, though in the latter case we'd have to take some care to avoid 
excessive amounts of duplicate code in the binaries, avoid symbol 
collisions, and make sure it is possible to load multiple drivers that 
depend on different versions of the library.

I don't think the solution to the common-code problem is to have one giant 
complex driver that tries to support every device.

> is there any way we can obsolete openct by having a driver
> for pcscd, that supports (almost?) every reader openct supports?
> for example adding drivers to ccid, or building several drivers
> from one common source?

It's possible that, rather than a library, it might work better to pull 
more drivers up into the pcsc-lite distribution and build them from common 
source.  The main problem with that is that it puts the burden on Ludovic 
to maintain them, or at least coordinate their maintenance.  I'm not sure 
that would be all bad, but I'd rather be stuck with the current level of 
duplication than have Ludovic give up because the job has become too big.

I've been speculating for a while now that it might not be too hard to 
produce a sort of driver adapter which would plug into pcscd in the same 
place as any other ifdhandler, and work by communicating with openct 
drivers.  This would let us get support for any devices for which openct 
has drivers, and might ease the path for people who want to provide drivers 
but find pcsc-lite's interface too painful to work with.

-- Jeff
_______________________________________________
opensc-devel mailing list
[email protected]
http://www.opensc-project.org/mailman/listinfo/opensc-devel

Reply via email to