@jcolebrand wrote:
via cgi-style interfaces.
They changed it, I believe in Apache2, so that it's no longer CGI specific, however the style is that you hook into the Apache runtime. The same is said about IIS and ASP.NET. There are at minimum two sets of processes running, there's the PHP process, and there's the Apache process. Ruby on Rails doesn't have that.
Talking about HipHop was specifically avoided because the question was in regard to the LAMP stack originally.
I didn't want to delve into the performance characteristics, such as how it fetches dynamic code vs static files vs caching vs FS response times and how it dumps raw data from a FS driver into the output stream, without reading it into the Apache runtime itself.
I also didn't delve into CDNs or how we could cache static elements in a caching application in front of the Apache or Rails implementation.
Sorry for the lack of depth on the response, and how I tried not to add too many layers of indirection into the analysis for the sake of brevity.
