Hi! I was about to apply the patch with additionl configure option but I now noticed that:
> + gnupg_sleep (1); This is a no-go: It would drop performance too hard. We often call a dozen gpg processes per second and having each one to last at least a second decreases application performance in an inaccepatble way and, rightfully, user will report a bug. Doing this in the gpg-agent _might_ acceptable (because it is a long lasting process). For gpg, gpgconf, gpgsm, gpg-connect-agent, gpg-check-pattern it is a no-go. Did you actually tried to use gnupg in a real world application (reading and sending mails to several recipients, or browsing a list of signed mails)? What about codumenting your effort and providing a patch, so that ppl can apply it if they feeel they need it? Shalom-Salam, Werner -- The pioneers of a warless world are the youth that refuse military service. - A. Einstein
openpgp-digital-signature.asc
Description: PGP signature
_______________________________________________ Gnupg-devel mailing list Gnupg-devel@gnupg.org https://lists.gnupg.org/mailman/listinfo/gnupg-devel
