> >Why would you go out of your way to create fragile code when you
> >could fix
> >this the right way in three or four minutes?
> If you don't use a "thread per request" model, it's a lot more than
> three or four minutes.
I don't see why you think that is. None of my code uses a 'thread per
request' model and implementing OpenSSL locking was as simple as a few dozen
lines of code. It's only that long because of extra debug and tracking in
non-release builds.
> I'd rather there were a public API to do this "pre-calc" kind of thing.
I don't think it makes sense to try to support a multithreaded model
without locking. The code will inevitably be fragile. I do agree that it
makes sense to have a public API to do the "pre-calc" for other reasons,
however, trying to guarantee proper operation without locks leads to
madness.
DS
______________________________________________________________________
OpenSSL Project http://www.openssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
