This is a little off topic.. but since we tend to test things locally (localhost) first prior to moving on to remote servers, I have questions regarding Apache setups.
I was looking into what exactly fastCGI is and what mod_php is. The wikipedia results seems pretty descriptive.
So if I understand this properly, fastCGI is an overhauled version of the orginal legacy CGI, and as a result is faster and can handle more webpage requests more easily.
mod_php on the otherhand is an embedded interpreter, which can interface with the server more quickly (and handle more webpage requests as well?).
According to the article, the downfall to mod_php is that it cannot be restarted independantly while fastCGI can. And as a result, many hosting providers prefer this. I wonder about a few things.
In what conditions would a hosting provider need to restart fastCGI? Is this for say PHP upgrades for instance? The article refers to things like 'facilitates per-application security policies — important for ISPs and web hosting companies.' Policies meaning?
Is there any benefits whatsoever of whether you install Apache on your local machine as fastCGI or going the route of module?
And tied into the previous question, as a result, does it make a difference whether your hosting provider runs Apache as fastCGI or as a mod?