Martin Lichtin wrote: > > Ok, but why then does the SSL patch subvert that behaviour?
That's a question Ben will have to answer.. > In general, module initialization can be costly, so Apache shouldn't > initialize all its modules twice at startup, there's just no reason > for it, as far as I can see. Well, please accept that there *was* a reason for it in Ye Olden Dayes, even if it seems not to apply now. And there's a reason for it now, as you've found: so as not to break 3P modules which expect it. This area was discussed last Summer and the dual-init behaviour confirmed (at least for 1.x). I think there may have been more to the reasoning than just obeying the Principle of Least Astonishment for 3P module authors.. #ken P-)} Ken Coar <http://Web.Golux.Com/coar/> Apache Group member <http://www.apache.org/> "Apache Server for Dummies" <http://Web.Golux.Com/coar/ASFD/>
