"Karl Scheibelhofer" <[EMAIL PROTECTED]> wrote in message
004a01bf6324$1665dc50$[EMAIL PROTECTED]">news:004a01bf6324$1665dc50$[EMAIL PROTECTED]...
> ----- Original Message -----
> From: Tom McKearney <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Tuesday, January 18, 2000 7:33 PM
> Subject: Re: [OCF] Re: Question on CardServices
>
>
> > So, if I understand you correctly, you want to be able to use Smartcards
> > without knowing anything about them? Good luck!
> >
>
> no that's not true. i want to know a lot of details on the cards i use.
but
> i don't want to implement every default driver for my own. i think for
this
> reason CardServices were developed.
> i rather bind my products/developments to a standard than to a specific
> vendor. and when i begin to develop CardServices/Applets for my own i have
> to adapt them for every new card. no thanks. i think this should be up to
> the card vendor.
No, CardServices weren't developed to help you with smartcard development.
They were developed to help you USE the smartcard programs you develop.
If you use any Multi-application card (JavaCard, MULTOS, etc.) then you'll
have to write NEW CODE for every kind of smartcard you want to support. If
you're lucky, none of those vendors are using non-ISO extensions to the
standard. If so, you _might_ be able to use the same CardService for that
(though you'll have to modify your CardServiceFactory to recognize the
additional cards).
If you're using standard CardService -=> interfaces <=-
(FileSystemCardService, etc.), then the card vendor needs to supply these.
If they don't supply them, it is NOT the Opencard Consortium's fault, it is
the card vendor's fault, and _your_ problem to solve by either: 1) Choosing
a different card vendor, or 2)Implementing the standard -=> interface <=-
yourself.
Also, please note that the standard interfaces like FileSystemCardService
all use _proprietary_, non-standard card-specific functions provided by the
card vendor. Thus, you will NOT be able to use the same class to access
different vendors cards.
Tom McKearney
---
> 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.
