RE: [PHP4BETA] JSP vs. PHP - Two vs. Three Teir

Never mind I found them. A snake would have bit me. thanks!again PHP community comes through again ;) -----Original Message----- From: Michael Nino Sent: Thursday, April 06, 2000 3:04 PM To: ; Michael Nino; rubys@us.ibm.com Cc: php4beta@lists.php.net Subject: RE: [PHP4BETA] JSP vs. PHP - Two vs. Three Teir Okay. So what your saying is when a PHP service (or PHP script with no timeout) is called it run in memory servicing what ever requests-- may via a socket or shared memory to other PHP scripts executing, right? If so, what are the names of the functions to access shared memory in PHP and I think I'm ready to give it a stab! ;) thanks for you repeated replies! -----Original Message----- From: Peter Kocks [mailto:peter.kocks@baygate.com] Sent: Thursday, April 06, 2000 2:25 PM To: Michael Nino; rubys@us.ibm.com Cc: php4beta@lists.php.net Subject: RE: [PHP4BETA] JSP vs. PHP - Two vs. Three Teir It'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