On Tue, May 30, 2006 at 06:59:26PM +0200, Henryk Plötz wrote:
 
> Also the build process is currently somewhat complicated because a
> librfid ifd handler needs to have librfid, but librfid needs openct a
> part of which is the librfid ifd handler. Some way to decouple these
> dependencies? (E.g. dynamically loadable ifd handlers like for
> pcsc-lite).

that indeed poses some room for problems, yes.

> The current way of having an openct ifd handler calling a library that
> calls another openct ifd handler seems to be ugly. For the future it
> would be nice to have the contact-less support in the same ifd as the
> contact-based part, e.g. as an additional slot (or even several slots,
> because I've been told that 4 cards should be possible). This would
> also nicely solve hotplug. Of course the most easy way would be to
> subclass the ccid handler, if there was something like subclassing in C.

yes, I don't really like that architecture, too - but it was the easiest
I could come up with, mainly because of the peculiar architecture of the
cm5121, and because I didn't want to hack all the RFID stack into the
ifd-ccid, which is clearly not where it belongs.

Also, thinking of other readers such as Philips Pegoda, the API /
abstraction layer split is again at some other point.  Here we have a
reader that is purely contactless, and therefore has no relation to CCID
whatsoever.  

In that case librfid would (not yet there, but on my way) provide its
own hardware-specific driver that in turn resembles a
rfid_asic_transport, on which the rfid_asic_rc632 layer and the rest
resides.

So I guess nobody will be able to give you the answers you need.  Just
go forward with it and come up with anwers.  If it was _that_ easy,
somebody else would have done it before you ;)

Thanks for your time,
-- 
- Harald Welte <[EMAIL PROTECTED]>                      http://gnumonks.org/
============================================================================
We all know Linux is great...it does infinite loops in 5 seconds. -- Linus

Attachment: pgpQQVaR7Ow2w.pgp
Description: PGP signature

_______________________________________________
opensc-devel mailing list
opensc-devel@lists.opensc-project.org
http://www.opensc-project.org/mailman/listinfo/opensc-devel

Reply via email to