Swap 'client' and 'server' terms, please. When apache connects to FastCGI application, application is the server, and apache is the client, because apache/mod_fastcgi sends _request_ and application _serves_ it. Client requests, server replies. Browser is the client for web-server, but web-server is the client for application(s) server(s).
Yes, "server" is not really a good description. It's the server side of the equation, but the server is a client of the FastCGI protocol, in that the server requests and the FastCGI app responds. This is the same problem with X terminology.
Really we should have words that mean closer to human/user and further from human/user, because this is often what we are really concerned about, or can most easily understand when considering the architecture. Note that developers don't count as humans in this equation ;)# Ian Bicking