> Of course, the more popular languages weren't implemented > with embeddability (embedibility?) in mind. [...] > safely embedded in a multi-threaded application.
I intended to reply to an earlier message regarding the suggestion that we try to support PHP in AOLserver, but Dossy's observation about thread-safety jogged my memory. There is (was?) a libphp.so for AOLserver, but it has been notoriously unstable. It stability is directly tied to the lack of thread-safety in PHP loadable modules. In addition, lots of PHP applications depend on stuff provided by Apache (mostly Apache-set environment variables) that AOLserver does not also provide. Several years ago I spent a substantial amount of time trying to get Imp (the IMAP webmail client) running in AOLserver--I abandoned the project when I realized that the thread-safety was just not there. The bottom line is that it's not sufficient to simply provide PHP in AOLserver, it would have to be PHP with enough "Apacheness" added to allow it to be a drop-in replacement for the huge number of PHP applications out there. --cro -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
