29 ms·
I do have fond memories of the simplicity of CGI, but also remember the big speedup and scalability improvement when we swapped over to NSAPI (no more forking,
by tyingq 6y ago
I do have fond memories of the simplicity of CGI, but also remember the big speedup and scalability improvement when we swapped over to NSAPI (no more forking, pooled processes, etc).
Kind of interesting that "serverless" (AWS Lambda, etc) seems to be going through the same evolution now. That is, initially liking the simplicity then hitting a wall with performance and making it more complicated.
- jandrese 6y agoI still think Lambda was just CGI tarted up and sold as a whole new thing. There was a transition period where people were trying to still use CGI but make it scale so you had things like CGI mod_perl in Apache.
- tyingq 6y agoAh, yeah...mod_perl did make a nice bridge for Perl stuff. I had mentioned NSAPI because we had C++ CGI and NSAPI was available before things like FastCGI.
- Nursie 6y agoBeen thinking this recently, lambda is a return to CGI, you provide a small program that runs and provides its results to something which sends them back to the client.
- tpmx 6y agoFastCGI was the standardized approach. See also: https://news.ycombinator.com/item?id=24683304 https://news.ycombinator.com/item?id=24683304 ("FastCGI – The Forgotten Treasure (2002)")
- tyingq 6y agoSure. Wikipedia mentions FastCGI initially being a reaction to NSAPI. "Open Market originally developed FastCGI in part as a competitive response to Netscape's proprietary, in-process application programming interfaces (APIs) (Netscape Server Application Programming Interface (NSAPI)) for developing Web applications"
- tpmx 6y agoOh, I'm showing my ignorance here - I didn't know NSAPI was in-process. The Netscape server software was expensive and kinda hard to find in Europe back then. I guess FastCGI was an improvement in terms of stability - I'm assuming the NSAPI was .so/.dll-based? So if you messed up, the entire server went down. Back in the mid 90s I worked on the Spinner/Roxen webserver that was built on an interpreted C-like language modelled after the LPC language being used for MUDs. Modules were were run in-process, but because of the interpretation a failure resulted in an exception/error, rather than a full crash. This software didn't get very popular - we sucked at marketing.
- deleted 6y ago[deleted]
- tyingq 6y agoMost people kept the in-process stuff down to something that worked like Fast-CGI, just proxying requests to some non-NSAPI persistent process over a socket.
- tpmx 6y agoSomehow this ended up at Oracle? That's just nasty. https://docs.oracle.com/cd/E19146-01/821-1833/index.html https://docs.oracle.com/cd/E19146-01/821-1833/index.html