From: Jost B. <jos...@ya...> - 2005-06-21 18:59:12
|
Hi, I am not sure where this is from, but I can assure you that the information quoted below is wrong. As I understand it, it's exactly the other way 'round. The bridge should work better in a process environment than in a threaded environment. For several reasons; for example every time a threaded http server aborts the execution of a module and the shutdown hook of the module is not called, the server may leak resources (socket handles, memory etc.). Furthermore there is no process barrier, the php module in one thread may read the data of a php module running in another thread. Even though a http server creating processes (e.g. Apache 1.3 or 2.0 with prefork MPM) responds slower than a threaded server (e.g. IIS or Apache 2.0 with thread pool MPM), I would recommend it for php modules. Anyhow, the above discussion doesn't apply to the PHP/Java Bridge. It doesn't matter whether you run the java.so in a process- or threaded environment. The native code in java.so simply forwards requests to a Java VM running in a different process, and, if SEL is enabled in the kernel, even in a different domain. Regards, Jost Boekemeier sachin jain <sac...@re...> schrieb: HI all, I want to install PHP/JAVA Bridge on Suse Linux. I saw a mail in PHP mailers list part of it is given in following para. "Thomas 25-Feb-2004 03:44 The documentation is missing an important note: The PHP/JAVA bridge only works on threaded http servers such as IIS, it does NOT work on http servers such as APACHE which fork off (sub-)processes." Can anyone clear this doubt wether APACHE supports and works fine with PHP/JAVA bridge or not. Thanks in advance Regards, Sachin --------------------------------- Gesendet von Yahoo! Mail - Jetzt mit 1GB kostenlosem Speicher |