Le jeudi 25 septembre 2003 � 14:47:33, Damien Sauveron a �crit: > Hi, Hello,
> Have you some ideas for a new design? I think we will need: - one thread for plug/unplug of readers - one thread for getting client connections this "mother" thread forks for each new client so each client will have a different thread when talking to a different reader. So each client talking to a different reader will be managed by a different thread. And it is the jobs of the kernel scheduler to avoid starvation among the threads. Of course we will have to be carefull to avoid dead-locks and other funny things. I don't know if we need to stabilise the 1.2.0 version as it is now and include this new feature in a 1.3.0 version or if we include this work now in 1.2.0 and will not have a stable official release before a long time. I am happy with the version we have in CVS (only one, easy to include, feature request on alioth tracker [1]). But I cannot test pcsc-lite on all the platforms pcsc-lite is supposed to support. What do you (the muscle community and pccs-lite users) think? Regards, [1] https://alioth.debian.org/tracker/?group_id=1225 -- Dr. Ludovic Rousseau [EMAIL PROTECTED] -- Normaliser Unix c'est comme pasteuriser le camembert, L.R. -- _______________________________________________ Muscle mailing list [EMAIL PROTECTED] http://lists.musclecard.com/mailman/listinfo/muscle
