Gilles Ganault a écrit :
So it looks like, unlike PHP, the prefered solution in Python is to build a complete application as a long-running process, and either use its embedded web server or configure a stand-alone web server to act as reverse proxy using either FastCGI or WSGI to connect the two.
Yeps. You'll find the same pattern with most general purpose programming languages, and specially OO ones.
The PHP execution model (mostly based on CGI FWIW) tends to be a bit unpractical for non-trivial applications since you have to rebuild the whole world for each and any incoming request, while with a long-running process, you load all your libs, parse your config etc only once.
Also, gateways like FastCGI or WSGI avoids being tied to a specific web server.
-- http://mail.python.org/mailman/listinfo/python-list
