Please answer if you know the following question I'm going to ask. I'm looking
now for the best way to make our current resource manager available to
applications. What is the best way ? If the Resource Manager was a shared
object with some variables declared statically would multiple apps be able to
load and then communicate with the object simultaneously ? Or do I need to
interface with the kernel somehow by making the resource manager attached to a
device. Or maybe we could make it a daemon upon startup but then you have to
deal with interprocess communications.
Say we created a library that loaded the resource manager's shared object which
was located in /usr/lib/. That library would contain all the necessary
function calls to be able to communicate with the resource manager. This would
leave the dynamic loading/etc hidden to the App programmer.
What are the pros and cons here.
Once we make a decision, I will finish the resource manager as 1.0beta and the
app programmers can have at it. I have hacked together a ctapi for the
Towitoko ChipDrive which works wonderfully with the resource manager. I'm
still working on MCT but should have that working soon.
Thanks
Dave
--
******************************************************************
David Corcoran Internet Security/Smartcards
Work: School:
205 Industrial Blvd 2252 US Highway 52 West Apt C4
Sugar Land, TX 77478 West Lafayette, IN 47906
Suggestion: Use Linux, it is for IQ's higher than 95.
Quote:
If you can't make it work, at least make it look good.
~ Bill Gates
******************************************************************
***************************************************************
Linux Smart Card Developers - M.U.S.C.L.E.
(Movement for the Use of Smart Cards in a Linux Environment)
http://www.linuxnet.com/smartcard/index.html
***************************************************************
