Ludovic Rousseau wrote:
On 25/10/06, Paul Klissner <[EMAIL PROTECTED]> wrote:
Just in time for another diagram update:
http://www.freemyimage.com/ims/pic.php?u=1500BLfhm&i=15920
Why do you have: "The IFD handler plugin directory location specified
in argv[]"?
Do you need to have different drivers for different zones or DTUs?
Bye,
The current thinking is to pass in a base directory
into argv[] where pcscd will find it's other configuration
files, such as reader.conf, and what, by default, goes into
/var/run. This is because we are creating a daemon for
each client session, each requiring it's own unique
repository for private non-shareable data.
I have to let Mike answer why the plan was to indicate the
IFD handler directory with a separate runtime specifier.
That's his idea, and I'm not totally positive was to why.
I think the goal is to be able to optionally put all of
the pcscd data in it's own unique directory tree, so that
although there would be only one copy of the IFD handlers,
symbolic links to them could be put in each pcscd's
data directory tree, I supposed for the sake of simplicity,
locality, architectural elegance or something.
Paul
_______________________________________________
Muscle mailing list
[email protected]
http://lists.drizzle.com/mailman/listinfo/muscle
