> Why don't you just create a daemon started from the command line > (shell/DOS) and have it accept socket connections from your Web server > PHP scripts and provide a SOA (Services Oriented API) to the code that > accesses your data structures pre-loaded in memory? Setting up a separate persistent daemon PHP script is appealing to me because It implements exactly what I want, which is a persistent PHP application server, and also would allow me to abstract the implementation behind an API, move it to other servers when load increases, etc. However, would a single process PHP server daemon be able to appropriately handle the incoming load from Apache, which will be running multiple processes handling concurrent incoming requests? Implementing a multi-process forking SOAP server in pure PHP seems inefficient, but maybe I'm not understanding the basic premise/implementation of the suggestion? Any good links/tutorials/examples/books for this? Thanks! /josh w. -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
