FastCGI was supposed to be better, but my experiments on Apache servers show it to be very close in performance to CGI when using mod_cgid (which tries to minimize fork() costs by running it from a tiny demon process, communicating with it over UNIX sockets iirc). My standing theory is that FastCGI was faster when CGI was more naive, or perhaps using older kernels where fork() might have been more expensive or something, but I don't really know for sure.
But anyway, my recommendation to write an Apache or NGINX module, or write a standalone server from scratch in assembly, are based on fun factor alone, not necessarily what I'd recommend for production. I'm more likely to recommend a CGI script for prod because other developers would be less afraid of working on it.
This post is sent from a #snac2 instance running as a #FastCGIOh, I run snac2 too, behind an Apache reverse-proxy,
didn't know it can run as a FastCGI script.
I will look that up, thanks :)
these forgotten technologies provide viable and cheap alternatives to #BigTechIndeed, just tell them CGI is "serverless functions" and everyone would clap and say big yes :D
http://www.tesio.it/2024/12/18/how-to-run-your-own-social-network.htmlI enjoyed this article, and learned about cgi-fcgi, thanks again.
https://code.tesio.it/p/self-hosting/doh.cgi/dir?ci=tipCurious. I usually host a dnscrypt-proxy server on my VPN, to allow all my devices to access secure DNS. Self-hosted DoH with CGI sounds pretty interesting. Also yay for fossil :)
Hack on, friend~