Hi, Further to my post yesterday I understand a bit more about the way OCF handles such things. In short: I want my application to talk to any multi-applet smartcard, using my own sequence of command APDUs. I see two possible solutions: 1) Use the BasicAppletCardService so send APDUs specifically to my applet, using OCF 1.2's ability filter out duplicate applet SELECTs. 2) Write MyOwnCardService that implements an interface for my service type. Both solutions require me to write my own CardServiceFactory and register it. It seems that BasicAppletCardService is not implemented for any of the smart cards that currently have service factories with OCF 1.2 Why is this? Anyway, there's not much difference in work between (1) and (2) as far as I can see, but I'll do (1) for the moment. Can somebody tell me if this is the right approach or not? Basically I don't care about the actual make of the card. If it doesn't support multi-applet operation or installation of applets, I can't use it anyway and the user will get an error. However, if nobody currently implements BasicAppletCardService surely there isn't much point implementing it myself and I should just use SlowChannel.sendCommandAPDU and say "to hell with other simultaneous card apps". Anyone have any info/views on this? As an "outsider", the world of smartcards seems to be a mess... which is not suprising as it is really in most manufacturers' interests to keep application developers working with one card type. Cheers --- > 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.
