Reinis Rozitis Wrote: ------------------------------------------------------- > >>From what I understand: > > - PHP offers no way to prematurely close the > connection except by setting and reaching > Content-Length > > While I havent it used myself so not sure if it > works 100% as expected there is such feature if > you use php with the FPM > patchby cactus - Nginx Mailing List - English
I was hoping for a different answer - I guess I'll just have to make a few of configurations and test what works best. Thank you for helping out! :)by cactus - Nginx Mailing List - English
Rob, thank you for the idea! We have used it before on other problems, though I had no idea there are libraries made to address this problem (I used my own solution). Thanks for the link, the projects there look very promising. However, the way I see it, this approach is only useful if you want to distribute the load across other machines or across time (so that major work is done when the loaby cactus - Nginx Mailing List - English
First of all - thank you for your answer, I really appreciate it. This is interesting - I have re-checked and it takes me 32ms to get the result on my development machine: Server Apache/2.2.9 (Debian) PHP/5.2.6-1+lenny4 with Suhosin-Patch X-Powered-By PHP/5.2.6-1+lenny4 (PHP is installed as mod_php) Still, it is very important for me to be able to postpone processing. If I can't do it onby cactus - Nginx Mailing List - English
Hi all! I am optimizing a few of the PHP scripts by: - doing all that generates output to browser - closing connection to browser - doing some more processing The processing bit cannot be avoided, but the speed of execution (from visitors' point of view) is awesome this way. The problem is that we have tried migrating the script to NginX + FastCGI (it works on Apache + mod_php) but it doeby cactus - Nginx Mailing List - English