On Thu, Jan 22, 2004 at 09:33:45PM +1100, Matthew Palmer wrote: > On Thu, Jan 22, 2004 at 10:24:14AM +0100, Arnaud Vandyck wrote: > > phpldapadmin and phpwiki were not usable with my modified php4-apache2 > > packages! > If you think the problem lies in phpwiki, by all means file a bug - > preferably with a patch that doesn't break operation for apache 1.3. But as > Donald Becker said, "Three of your friends throw up after eating chicken > salad. Do you think 'I should find more robust friends' or 'we should check > that refrigerator'?". > After talking to Rasmus last week about this very issue (and I was > originally skeptical of his claims), I believe that it will be *very* > difficult to get something the size of PHP4 working fully threaded. There's > just too many third-party libraries of varying quality out there that php4 > modules might end up using. I've heard tell that if the prefork model in > apache2 gets quicker, then that's an option, as is doing unpleasant things > with large scale mutexes - but they both totally ruin any performance gain > you might have had by going the threaded model. They really ought to take a page from the freeradius book, and include "is threadsafe, y/n" as a flag on their extension definitions. By including it in the extension API, they can ensure that the performance penalties only affect those users who actually *use* non-threadsafe libraries, instead of having the whole thing come crashing down due to the use of non-threadsafe libs. So if you talk to him again soon, maybe you can suggest this to him. I've been muttering this for years, but I don't think anyone pays attention to my mutterings. :) -- Steve Langasek postmodern programmer
Attachment:
pgpzEewcOzccz.pgp
Description: PGP signature