~15 years ago, I was tasked with implementing FastCGI support for a webserver I was writing in C++, so that it could proxy some downstream crud stuff written in Python. After mulling over it for a couple of days, I ended up implementing SCGI[1] support instead. SCGI is like FastCGI, but a lot simpler to parse, IIRC.
Yes, SCGI ranks even higher on the "forgotten" scale (not as sure about the "treasure" part). It's pretty great if you have to implement at least one end yourself (new http server, new connected language/framework).
One of the advantages of fcgi is that it can be launched "in place" like cgi, with the server restarting the backend every N requests. Does SCGI support doing this?
Comments
~15 years ago, I was tasked with implementing FastCGI support for a webserver I was writing in C++, so that it could proxy some downstream crud stuff written in Python. After mulling over it for a couple of days, I ended up implementing SCGI[1] support instead. SCGI is like FastCGI, but a lot simpler to parse, IIRC.
[1]: https://en.wikipedia.org/wiki/Simple_Common_Gateway_Interfac...
Yes, SCGI ranks even higher on the "forgotten" scale (not as sure about the "treasure" part). It's pretty great if you have to implement at least one end yourself (new http server, new connected language/framework).
One of the advantages of fcgi is that it can be launched "in place" like cgi, with the server restarting the backend every N requests. Does SCGI support doing this?