Carl, Selon Carl Youngblood <[EMAIL PROTECTED]>: > Thanks for the additional references. That helps. I was also > thinking: not only does the muscle PKCS11 library need to be updated > to fix this problem, but the musclecard library does too. Yes perhaps. I don't know the code of the Musclecard library.
> I agree that the ideal thing would be to fix the scheduler, but there > is often a wide gap between what is ideal and what is practical. For > example, if I am developing a program for public consumption, I can't > rely on the developers of my target platform to fix problems that I > find in their libraries. Even if I could get them to fix the > problems, people who had older versions of the libraries would not be > unable to run my software and would be dissatisfied with my product. Here I am not agree. People who have older version (i.e. bugged version) should update them if they wish to use our software. And even if you can not rely on the developers of your target platform you can fix the problems yourself. At least on open source platform, no? > If it is within my power, it is in my best interest to code > "defensively"--meaning that I should compensate for bugs in other > layers whereever possible. You are the one who is most familiar with > the code, so you know best where to update it and how to do it, but it > is worth considering that a few small workarounds could alleviate a > lot of problems for people who are using your libraries and increase > the perception of value, even if you end up fixing other people's > mistakes. Here I am agree with your reasoning but even if I know well this part of the code I don't see any solution for the moment. Actually I write my PhD Thesis I have not the time to work on the problem. Patchs are welcome. :-) > In saying this, I recognize that I also need to follow my own advice > and code defensively for problems that I might find in other layers. Good remark, I have not thought to this. :-) I hope we will find a solution satisfactory for everybody. Regards, -- Damien Sauveron ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program. _______________________________________________ Muscle mailing list [EMAIL PROTECTED] http://lists.drizzle.com/mailman/listinfo/muscle
