Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>You can <a href="http://www.python.org/dev/peps/pep-0333/#the-server-gateway-side" rel="noreferrer">run WSGI over CGI as Pep333 demonstrates</a> as an example. However every time there is a request a new Python interpreter is started and the whole context (database connections, etc.) needs to be build which all take time.</p> <p>The best if you want to run WSGI would be if your host would install <a href="http://code.google.com/p/modwsgi/" rel="noreferrer">mod_wsgi</a> and made an appropriate configuration to defer control to an application of yours.</p> <p><a href="http://trac.saddi.com/flup" rel="noreferrer">Flup</a> is another way to run with WSGI for any webserver that can speak <a href="http://www.fastcgi.com/drupal/" rel="noreferrer">FCGI</a>, <a href="http://www.mems-exchange.org/software/scgi/" rel="noreferrer">SCGI</a> or AJP. From my experience only FCGI really works, and it can be used in Apache either via <a href="http://www.fastcgi.com/mod_fastcgi/docs/mod_fastcgi.html" rel="noreferrer">mod_fastcgi</a> or if you can run a separate Python daemon with <a href="http://mproxyfcgi.sourceforge.net/" rel="noreferrer">mod_proxy_fcgi</a>.</p> <p><a href="http://wsgi.org" rel="noreferrer">WSGI</a> is a protocol much like CGI, which defines a set of rules how webserver and Python code can interact, it is defined as <a href="http://www.python.org/dev/peps/pep-0333" rel="noreferrer">Pep333</a>. It makes it possible that many different webservers can use many different frameworks and applications using the same application protocol. This is very beneficial and makes it so useful.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload