Wasn't FastCGI actually running a persistent connection, just like an HTTP connection but with a custom protocol for no good reason?
"Auto-scaled-CGI-as-a-service"
Name itself is important. It is faster and more efiecient than cgi
Yes, it was a local only binary connection. The key difference from regular CGI was not needing to start a new process for every request, so it could be used with languages with long VM startup time.
Yeah, that makes it Not CGI, so it's more like binary HTTP. I guess you could say, a precursor of HTTP/2 :)