Re: [phplib] The change to PEAR... From: Kristian Koehntopp (kris <email protected>)
Date: 01/19/01

In netuse.lists.phplib you write:
>A PHP application server as you describe is a great idea. I'm only
>surprised because I figured that the folks who developed mod_php had
>already done most of that -- i.e. the Apache instance (Unix process) is
>much longer lived, and mod_php could certainly have data stores which
>persist across pages. Somehow, I thought all along mod_php was smart
>enough keep connections in such a place, and with PHP4, sessions as
>well.

PHP 4 does keep connections when you are using pconnect to
establish them.

But: mod_php does run in the security context (under the UID of)
the webserver. This has two implications:

You cannot have multiple instances of mod_php running under
different UIDs.

You have many instances of mod_php running in different
processes, which cannot share connections. In an Apache with
MaxClients 100, you get 100 times the number of (host, user,
password) tuples connections to your database as a worst case
when using pconnect.

Also, there is no generic mechanism to keep variables, sockets,
files and other ressources around past a request.

>So...how soon can we have this PHP app-server, and how can I help make
>it happen?

Research how to run PHP in a multithreaded server, which for
example communicates via ONC RPC with a stub program. The stub
program can be a command line tool "phpclient" or a
mod_phpclient.so as part of Apache. Then modify the PHP
multithreaded server so that it includes a $SHARED[] and a
$SESSION[] array as I suggested. Finished.

Kristian

---------------------------------------------------------------------
To unsubscribe, e-mail: phplib-unsubscribe <email protected>
For additional commands, e-mail: phplib-help <email protected>