Re: How to handle concurrent requests with fastcgi?

I wasn't aware that it wasn't supported, as I've been unable to find clear documentation anywhere about it. The only thing that I knew was unsupported was FastCGI multiplexing, but the argument given in the newsgroups for why it wasn't (aside from PHP not supporting it) was that equivalent functionality could be gotten by nginx opening multiple sockets, so I presumed that that was supported - the fact that I never see multiple connections opened thus came as a surprise, as it has appeared to me that nginx is incapable of concurrent processing of FastCGI requests.

So, you're saying that the two ways I can get concurrent access to my application are:

1. Use nginx as an HTTP proxy and basically pass the HTTP requests to my application directly.
2. Use nginx's load balancing to set up a FastCGI loadbalancer, with a bunch of entries for... I suppose 127.0.0.1:PORT? I am unclear how this would work, as the documentation seems to presume I'm talking to remote machines with unique addresses. Would this even work?

http {
upstream backend {
server 127.0.0.1:9000;
server 127.0.0.1:9000;
server 127.0.0.1:9000;
}
server {
location / {
fastcgi_pass localhost:9000;
}
}
}

I feel like that would be invalid. Or would I need two instances of nginx running - one to handle load balancing, and one to receive the requests?