I was looking at the resource manager.. it looks like some stuff needs to
be done with the SCARDCOMM::Connect so that the access modes work
(exclusive, shared).. The spec refers to the SCARDMANAGER class as having
something to do with this in the SCARDCOMM description and in the
RESOURCEMANAGER
I am going to use the PF_UNIX internal socket implementation to talk to
the resource manager. It should be fairly simple and will also let me
easily implement external sockets when I create inter resource manager
communications between multiple machines. As Spafford is saying we should
make it
OK, I've been promising it for awhile. I have finally released a pre Alpha
version of Smart Manager. It does NOT yet integrate into the kernel so it is
still limited to 1 application since the application must be built on the
resource manager. I will SOON have it so you can load a library from
Ok, I have released a sample base for a resource manager. The code calls the
config file function to return key/value pairs from the config file called
config.txt. This function returns the location of the reader CT-API library
for the specified reader SLB_RF_60 (Schlumberger Reflex 60). The li
Now that the link is fixed I'll explain what we would have to do for the low
levels on a resource manager. On the top level or the level that is what the
Application uses we can write a PC/SC subset of commands for the Application to
talk to. Unfortunately there are some kernel issues here if
