Forgive me if I'm repetetive, since I'm new on the list, but I was
taking a closer look at the PC/SC specs last
night, and had some questions/observations:
The resource manager appears to be responsible for
* ICC identification and tracking.
* Allocation of readers for user applications.
* Ensuring that application/card functions are completed before
another application can access the reader.
In a networked environment running X, an app will sometimes be running
remotely on a server but displaying
on the client. In order for a reader at a client machine to be accessed
by the remote application, the resource
manager would have to be network aware in some way. My initial gut
feeling is that a daemon or inetd service
would be a nice way to do this...
For command line applications (ssh comes to mind) that might want to use
the card reader, the interface would
be better handled through the tty associated with the shell.
So the resource manager should be versatile enough to handle both local
apps and remote apps whether they
are command-line based or graphical (X).
If the resource manager was in the kernel, the above would still apply
at the service provider level...
Just some thoughts. I'm still "getting aquainted" with the specs and
have yet to actually get anything working
with the existing MUSCLE code... (I became aware of this project at the
Expo, so yes, I'm new to this)
Regards,
Mark
--
"Those who do not understand Unix |
are condemned to reinvent it, | Mark Jackson
poorly." | Software/Hardware Design
-- Henry Spencer | email:[EMAIL PROTECTED]
***************************************************************
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
***************************************************************
