Jeff Trawick wrote: >Please let's not get in any hurry replacing worker with this. worker >has problems but it is good enough to ship, and I'd rather see >incremental improvements to it since what we need now (IMO) is the >ability to get new GA releases out the door fairly quickly as our user >base ramps up and we fix problems that they discover. MPM redesigns >have always required a long shake-out period in the past. I don't >expect that this would be any different. > >I think it would be fine to add another MPM, and as people gain >confidence in it more people will use it and it may become appropriate >to zap worker down the road (maybe not much further down the road; I >dunno). >
I'm definitely not opposed to turning it into a new MPM, rather than a worker fix. Where's the right place to put a new MPM? server/mpm/[name] or modules/experimental? --Brian
