At 03:04 PM 8/15/2002, Justin Erenkrantz wrote: >On Thu, Aug 15, 2002 at 11:51:52AM -0700, Ian Holsman wrote: > > it's not as obvious, the proposal above forces the developer to say > > "i verify my module will work with threaded" > >No, I'd much prefer that modules code their own checks for it. A >simple check in the pre_config hook phase should be sufficient.
The answer "i verify my module won't work threaded" and emitting a warning [or outright error] should be more than sufficient. This allows PHP to collect the extensions it's loading and decide if thread safety is a hazard or those extensions are explicitly trusted for thread safety. I think it's bogus to state that Apache 2.0 is causing the pain. If you don't want to be loaded in a threaded server, say so in your preconfig. 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. Justin is right on here. Bill
