On Sat, Feb 14, 2009 at 9:45 PM, Martin Preuss <[email protected]> wrote: >> Can you please write the reasons why did you chose to access the >> reader directly and not use PC/SC within utilities? > [...] > > The base of the driver was created when PC/SC wasn't that popular under Linux, > so the developers at that time created a driver for the interface which was > at that time widely used. > > The driver is basically a CTAPI driver. We have a wrapper which makes it work > as an IFD driver as well (like the old Open Source Towitoko driver did), but > internally it is a CTAPI driver. > > Later, as PC/SC got more popular, the IFD wrapper was added, but still the > internals of the driver remained CTAPI. > > The tools also come from a time where CTAPI was most popular among the > customers. > > Many of the customers who use the cyberjack still use applications which only > work with CTAPI drivers (even Moneyplex is CTAPI-only) so currently there is > no immediate need to rewrite either the tools or the driver. > > Of course, that might change when Moneyplex and the medical applications > switch to PC/SC instead of CTAPI. >
Thank you for explaining that. This way I beleive that a separation between reader framework and application API is required, so a single framework may be used in order to support (for example) PC/SC and CTAPI without conflict and without rewriting the reader driver. Alon. _______________________________________________ opensc-devel mailing list [email protected] http://www.opensc-project.org/mailman/listinfo/opensc-devel
