3 ms·
Yes and no, respectively. A cgi-bin is as highly available as the web infrastructure hosting it, which as the cgi-bin author you don't need to know anything ab
by fooblat 5y ago
Yes and no, respectively.
A cgi-bin is as highly available as the web infrastructure hosting it, which as the cgi-bin author you don't need to know anything about.
A cgi-bin cannot "crash" because there is nothing long-running to crash. It is only run on demand.
I think it is easy to make the case that CGI was the proto-serverless api and that the serverless offerings we have today are an evolution of the CGI approach.
edit: typos
- mprovost 5y agoAnd cgi-bin was really just an evolution of inetd (or ucspi-tcp if you worshipped at the altar of djb). You didn't used to have to worry about binding to ports or long running processes. Something would just send you a message on stdin and you replied on stdout.