http://meat.net/2006/02/running-webpy-behind-scgi/ a blog Sat, 10 Jan 2009 00:37:50 +0000 http://wordpress.org/?v=2.2.2 http://meat.net/2006/02/running-webpy-behind-scgi/#comment-3931 Decorative Stone Fri, 15 Dec 2006 04:54:37 +0000 http://meat.net/2006/02/running-webpy-behind-scgi/#comment-3931 Great tip thanks. Great tip thanks.

]]> http://meat.net/2006/02/running-webpy-behind-scgi/#comment-328 eliott Wed, 05 Apr 2006 19:56:47 +0000 http://meat.net/2006/02/running-webpy-behind-scgi/#comment-328 My understanding is that the scgi code is just much clearner than the old fcgi code (which hasn't recieved an update in quite a while). I haven't yet tested any performance difference. I know lighttpd's fcgi implementation is pretty good. apache fcgi is notoriously bad. fcgid is supposedly an improvement, but I haven't had much luck with it. The Apache team is working on a replacement for both of these, from what I have been told. My understanding is that the scgi code is just much clearner than the old fcgi code (which hasn’t recieved an update in quite a while).
I haven’t yet tested any performance difference. I know lighttpd’s fcgi implementation is pretty good.
apache fcgi is notoriously bad. fcgid is supposedly an improvement, but I haven’t had much luck with it. The Apache team is working on a replacement for both of these, from what I have been told.

]]> http://meat.net/2006/02/running-webpy-behind-scgi/#comment-276 Andrew Ho Thu, 16 Feb 2006 06:02:22 +0000 http://meat.net/2006/02/running-webpy-behind-scgi/#comment-276 Perhaps in a future post you can explain why SCGI is better than FastCGI? Maybe I'm dense, but from reading the intro to SCGI, it sure doesn't seem very revolutionary to me. I didn't know sending headers and content back and forth was the interesting or especially unsolved part of the webserver framework puzzle! Perhaps in a future post you can explain why SCGI is better than FastCGI? Maybe I’m dense, but from reading the intro to SCGI, it sure doesn’t seem very revolutionary to me. I didn’t know sending headers and content back and forth was the interesting or especially unsolved part of the webserver framework puzzle!

]]>