Aktuelle Änderungen Printable View Änderungen Bearbeiten
EmacsVsVi > Enamel > EnterpriseApplicationIntegration > EnterpriseGuerilla > ErichGamma > ErichGammaConversations > ErikNaggum > Erlang > ExceptionHandling > Exceptions > ExecutablePseudocode > ExplorativeProgramming > Hacking > ExtensibleStylesheetLanguage > ExtremeProgramming > FastCGI > FastcgiOrModpythonClear TrailFastCGI operates on a client-server model, and in most cases you'll be starting the FastCGI process on your own. Your Web server (be it Apache, lighttpd, or otherwise) only contacts your Django-FastCGI process when the server needs a dynamic page to be loaded. Because the daemon is already running with the code in memory, it's able to serve the response very quickly.
Like mod_python, FastCGI allows code to stay in memory, allowing requests to be served with no startup time. Unlike mod_python (or mod_perl), a FastCGI process doesn't run inside the Web server process, but in a separate, persistent process.