My previous experience with FastCGI was not good, but I think that the problems we encountered can be overcome.
A few years ago I worked at a place that ran FastCGI under Apache. Each CGI script ran in its own process resulting in dozens of processes sitting around, usually doing nothing except consuming memory. Apache queued the requests to each CGI. You would get server busy errors if a CGI was slow and the default queue size was exceeded.
If there is a way to configure Fast CGI so that it can simultaneously attach to each thread in an AOLserver process then these problems won't be encountered.
