RE: [PHP4BETA] JSP vs. PHP - Two vs. Three Teir
| From: | Peter Kocks | Date: | Thu, 06 Apr 2000 21:24:57 +0000 |
| Subject: | RE: [PHP4BETA] JSP vs. PHP - Two vs. Three Teir | ||
| References: | 1 | Groups: | php.version4 |
| Request: | Send a blank email to php-version4+get-13254@lists.php.net to get a copy of this message | ||
RE: [PHP4BETA] JSP vs. PHP - Two vs. Three TeirIt's not clear to me what you
are trying to do. However, you may find it useful to use the
register_shutdown_function(). You can use this function to effectively
create a php service. After an initial connection the
register_shutdown_function is used to start a php service. You'll probably
also want to do set the script timeout to 0, and perhaps use a shared memory
segment to control the number of services running (i.e. if the shared memory
segment is set, then don't run the service).
-----Original Message-----
From: Michael Nino [mailto:mnino@Insight.com]
Sent: Thursday, April 06, 2000 1:50 PM
To: 'rubys@us.ibm.com'
Cc: php4beta@lists.php.net
Subject: RE: [PHP4BETA] JSP vs. PHP - Two vs. Three Teir
> In regards, to PHP functioning as a daemon or service to other PHP
scripts,
> can you think of any way this might be implemented?
Thanks for your comments. I neglected to mention the advantage we seek
when I say we would like PHP to run as a daemon or service. We would like to
take advantage for the "persistence" of the daemons/services ability to keep
data in memory (and possible communicate with other HTTP processes such as a
"watchdog" monitoring application status, connections to back, etc, etc...
Kinda like writing a a Apache module in Perl using sockets and shared
memory. Any ideas?
thanks!michael