On Thu, 15 Aug 2002, William A. Rowe, Jr. wrote: > There's no reason to bloat all of Apache and it's well behaved modules > with extra code, when only a handful of modules care to report that they > can't be compiled for a threaded architecture.
The strict engineer in me agrees. The pragmatic engineer in me realizes that threading issues are hard, and that you're going to get more false positives (modules allowed to run who shouldn't be) if you make threading opt-out rather than opt-in. It's not like this code (or flag) has to be handled on every request. [Just in case that wasn't clear - modules should indicate that they are thread-safe, else the threaded MPMs should abort. Perhaps it would be sufficient to simply report an error or alert in the logs, so that when things go wrong, it occurs to the admin to consider thread-safety issues alongside other issues.] When it comes down to it, we're only talking about a couple extra lines for all of the standard modules to indicate that they are thread-safe. While that road does lead to creature feep, non-thread-safe code running in a threaded program can be very touchy, likely to work in a large number of cases, while crashing with weird, hard-to-debug symptoms. Later, scott