Changes between Version 16 and Version 17 of ServerArrangements

Timestamp:

Jun 12, 2006, 3:31:24 AM (18 years ago)

Author:

James Bennett

Comment:

Explain why CGI is a bad idea

ServerArrangements

@@ -41 +41 @@
 For the code, see [http://bitprophet.org/code/django_to_zope.py this partly documented file]. It's in a temporary location for the time being; when I get a blog set up, I plan to complete the explanation and post it. For more info, drop an email to ''jeff (at) bitprophet (dot) org''.
 
-== normal CGI ==
+== CGI ==
 
-What's about normal pure CGI???
+Running Django as a traditional CGI is possible and would work the same as running any other sort of Python CGI script, but is generally not recommended.
+
+With traditional CGI, the program which will be run -- in this case, Django plus a Django-powered application -- is loaded from disk into memory each time a request is served, which results in a significant amount of processing overhead and much slower responses. FastCGI and SCGI, in contrast, load the code only once -- when the server starts up -- and keep it in memory as long as the server is running, resulting in much faster responses.