Peter Williams wrote:
Lets say I'm a PC application, and I write some data (which happens to
be a muscle APDU) to the IN object, using a WriteObject PDU.
I thinking now of adding a muscle command to the javacard which causes
the javacard to read the APDU stream in IN, and "send itself" the APDUs
therein encountered by setting up the global JCE buffers suitably for
IN, and then calling process(), recursively.
Would this be feasible to do!?
Hi,
as other things, in the software area everything is possible, especially
when it is open-source. If we cannot feed the stored APDUs in the JCE
buffers, we can surely provide them in an another buffer, and change
the code so to use a provided buffer, instead of getBuffer(). This does
not really matters.
What really matters is: how would you use such functionality ? What
would it be worth for ? Could you provide an example of how such
functionality would help in doing something in a somehow more meaningful
way than you would do with the protocol as it is right now ?
The idea is that the IN object (or any identified object, really)
becomes a simple stored procedure, basically.
Then, I guess you would like to store the APDU results into the output
object, in some format.... :-)
Bye,
T.
_______________________________________________
Muscle mailing list
[EMAIL PROTECTED]
http://lists.drizzle.com/mailman/listinfo/muscle
_______________________________________________
Muscle mailing list
[EMAIL PROTECTED]
http://lists.drizzle.com/mailman/listinfo/muscle
