Ivan Ristic wrote:
How is a persistent database connection handled then? e.g. in the
mysql module?
Apache 1.x pre-creates a number of server processes. Each process
handles a certain number of requests (one at a time), and then
dies. It is then replaced with an another server
Ivan Ristic wrote:
From the web serving point of view it isn't. Since Apache usually
interfaces to all kinds of modules and programs, the fact that
processes die naturally from time to time helps remove cumulative
errors.
IMHO this is a last-resort safeguard to prevent a system from
From the PHP point of view, you can get problems with persistent
database connections on a very high load site, that's true. But
that's about the only problem. Sure, you can't build a persistent
storage of information in the server but that's a minor issue.
It's not a minor issue.
Ivan Ristic wrote:
Right, but you can still use shared memory, or, you can store
persistent objects onto the filesystem. We've done the later
with satisfactory results.
Point taken. But this only allows to share resources that can be copied
into and from IPC shared memory. Some resources
On Thu, 5 Dec 2002, Maróy Ákos wrote:
Ivan Ristic wrote:
Right, but you can still use shared memory, or, you can store
persistent objects onto the filesystem. We've done the later
with satisfactory results.
Point taken. But this only allows to share resources that can be copied
Derick Rethans wrote:
Have a look at www.vl-srm.net, and more even the article about it @
http://www.vl-srm.net/doc/articles/php-almanac-2002.php (the part about
Bananas might be th emost relevant thing).
Thanks for the info. Though I could implement a similar deamon in java,
and call it
There is a servlet which accepts requests and uses native
code from libphp4.so to execute them. At the same time,
the Java extension is used to provide access to Java
objects from PHP itself.
but the ext/java as it is would not be suitable, as it would spawn new
JVMs every once in a
Ivan Ristic wrote:
No, I have been told (by someone, I do not remember) that if you
use PHP as a servlet ext/java would use the same JVM. I haven't
check to see whether that is correct.
sound good, I'll take a look.
Akos
--
PHP Development Mailing List http://www.php.net/
To
Ivan Ristic wrote:
No, I have been told (by someone, I do not remember) that if you
use PHP as a servlet ext/java would use the same JVM. I haven't
check to see whether that is correct.
My experiences:
using php-4.2.3, calling plain php pages from Tomcat seem to be OK. But
when calling
What I'm looking for is that the JVM would not be discarded on a regular
basis, but it would remain persistent.
I do not think that is possible, unless PHP engine itself
is contained within a single process (and runs multithreaded).
Which it isn't (under Apache 1.x , at least).
You
Ivan Ristic wrote:
I do not think that is possible, unless PHP engine itself
is contained within a single process (and runs multithreaded).
Which it isn't (under Apache 1.x , at least).
I'm not familiar in general with the PHP engine, so my questions may be
quite stupid. Anyway:
How is
--- Akos Maroy [EMAIL PROTECTED] wrote:
Ivan Ristic wrote:
I do not think that is possible, unless PHP engine itself
is contained within a single process (and runs multithreaded).
Which it isn't (under Apache 1.x , at least).
I'm not familiar in general with the PHP engine, so my
Brad LaFountain wrote:
Are you sure its getting unloaded or is it starting up in another httpd?
I'm not sure which. The only thing I see is that global static variables
in the shared object have their values re-initialized.
Akos
--
PHP Development Mailing List http://www.php.net/
To
How is a persistent database connection handled then? e.g. in the mysql
module?
Apache 1.x pre-creates a number of server processes. Each process
handles a certain number of requests (one at a time), and then
dies. It is then replaced with an another server process. The number
of
14 matches
Mail list logo
