It seems to be not the 'core' of PHP, but several of the modules that go with it aren't thread-safe.
Apparently, this really only shows up in the real world under heavy usage, and using the prefork "multi-processing module" should reduce or eliminate the potential problems. I think.
It SOUNDS like the warnings about not using PHP with Apache2 is mainly overcautiousness - every time one of these stories comes up, a few people pop up and say it's working fine for them, and I don't remember seeing anyone pop
Just to be the voice of dissention... I'm apparently the one person in the world for whom the PHP+Apache2 combo doesn't actually work right. Yes, it mostly works, but I'm constantly having to close out the windows that pop up when a thread goes boom. Yes, I am running it on XP (with all of the necessary service packs and hotfixes), but that shouldn't invalidate the fact that PHP+Apache2 isn't production-quality stable. And yes, I am 100% sure it is PHP causing the problem, as the errors only started whe
I've been running PHP/Apache 2 for a while... (Score:4, Interesting)
...and haven't noticed any problems. Why is this advised against?
Re:I've been running PHP/Apache 2 for a while... (Score:5, Interesting)
It seems to be not the 'core' of PHP, but several of the modules that go with it aren't thread-safe.
Apparently, this really only shows up in the real world under heavy usage, and using the prefork "multi-processing module" should reduce or eliminate the potential problems. I think.
It SOUNDS like the warnings about not using PHP with Apache2 is mainly overcautiousness - every time one of these stories comes up, a few people pop up and say it's working fine for them, and I don't remember seeing anyone pop
Re:I've been running PHP/Apache 2 for a while... (Score:4, Informative)
Re:I've been running PHP/Apache 2 for a while... (Score:0)
Re:I've been running PHP/Apache 2 for a while... (Score:1)