> Second and most important though, Apache isn't architected to handle long > running processes inside a request, as it typically uses a limited pool of
Not true.. Tomcat supports comet, and it runs on APR. Yes, the thread pool is small, but there is always a solution. The idea is to return the thread back to Apache's thread pool while waiting for an event: http://tomcat.apache.org/tomcat-6.0-doc/aio.html None of the workarounds (like polling, locking, etc) will work, the only real fix is to release the thread back to the pool. Or write a standalone process, but then it will need its own IP since running on a different port is known to cause problems with transparent proxies. Anyway, I'm positive that its doable.. Those Java guys have it already :) -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
