As Mladen hints, this was just 'the way it was done' since the Apache 1.3
MPM was first created. I began to set up more of the structures for having
parallel running httpd's and Mladen took this one step further with his
winxp mpm, but the bottom line is that resource sharing just doesn't work
the same way on windows as unix, and things like interlocking parallel
writes by two processes to a log file, for example, still need additional
work to behave without a huge performance hit.
So you are strictly asking if winxp will ever become more tolerant of the
processes crashing due to bad code?
By 'bad code' you're referring to code written by app developers? I
suspected I fall into that category, but even when I throw in all the
eval traps, the .dll errors still come to crash (and automatically
restart) apache.
I don't mind if performance is hit with the windows implementation of
modperl, since the usage is not exactly ebay load. But having
unpredictable cases of apache restarts - and a windows error message
popping out to state that fact - does give my administrators weak hearts.
I think the general game plan is that developers are able to rely on the
Windows platform for general deployments. The Linux/ FreeBSD alternative
is really when they need extra muscle for the job.
What with Java/ Ruby/ PHP/ .Net already working reliably on Windows,
it's difficult for modperl evangelists to convince their bosses that a
good language/ framework does not need to prove itself on the most
popular OS to date.
