Hi Cristopher,
it's right that you must explicitly refer to services but that doesn't negate
vendor interoperability. In the opencard.opt package are interfaces defined
such as
SignatureCardService or FileAccessCardService (used for cards with ISO
filestructure).
Vendors have to implement these interfaces ( and I think Gemplus did ) and
that way you
can request a card that supports for instance 'SignatureCardService'
independent from the
vendor that provides it. All you have to do is adding the
CardServiceFactories of the different vendors to your opencard.properties file.
Kind regards
Gunnar Osterode
> From what I have seen, the API allows a developer to create an
>application that "should" be interoperable with most smart cards. Yet why
>is it that in order to do basic things, the code must explicitly refer to
>services specific to the vendor of the card which negates the vendor
>interoperability.
---
> 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.
