"Gary Boon" <[EMAIL PROTECTED]> wrote in message
884a1i$uem$[EMAIL PROTECTED]">news:884a1i$uem$[EMAIL PROTECTED]...
[snip]
> My final point is, the main reason of a standard or framework such as OCF
is
> to allow the end user to change their, in this case, smartcard readers,
and
> alllow the client application to still execute. It seems at present OCF
has
> not reached the age of maturity where this can be said to be true.
Well, this problem rests solely on the towitoko people, because I'm using
PCSC with 3 different smartcard readers through OCF, so it's not an OCF
problem. Almost all the time, this is a problem with the drivers provided
by the manufacturer. Thus, you can not blame OCF.
I _will_ agree, however, that it is pretty lame for the Towitoko folks to
make a reader that doesn't work with OCF without tweaking. That just seems
counterproductive considering they're in the OCF consortium.
My point is this: If most people are having a problem with Towitoko
ChipDrive readers and that people don't seem to complain about GemPlus,
Litronic, SmartDisk, etc. then the problem does not lie with OCF.
Otherwise, these complaints would come from everyone.
Call Towitoko and yell at them.
---
> Visit the OpenCard web site at http://www.opencard.org/ for more
> information on OpenCard---binaries, source code, documents.
> This list is being archived at http://www.opencard.org/archive/opencard/
! To unsubscribe from the [EMAIL PROTECTED] mailing list send an email
! to
! [EMAIL PROTECTED]
! containing the word
! unsubscribe
! in the body.
