3 ms·
CGI is fine for unfrequently accessed pages on a machine that has some other purpose. Say, a stats / monitoring page on a file server, or something similar. [F
by nine_k 4y ago
CGI is fine for unfrequently accessed pages on a machine that has some other purpose. Say, a stats / monitoring page on a file server, or something similar.
[FastCGI] keeps most of the CGI's simplicity of the interface, while keeping the worker processes running, instead of starting a fresh copy every time. It's very widely used to this day.
[FastCGI]: https://en.wikipedia.org/wiki/FastCGI https://en.wikipedia.org/wiki/FastCGI
- tannhaeuser 4y agoCGI can be used for high performance sites/routes when used with HTTP caching. Though CGI leaves response time on the table by taking arguments via the environment such that you can't start/pool CGI processes before requests are arriving. FastCGI needs multiplexed transport of HTTP traffic in to and out of a single process, changing code complexity drastically and taxing memory management. It's far from keeping CGI's simplicity.