CGI vs WSGI

[tuom.larsen]

Dear all,

what is the difference? Middleware?

I'm wondering because the only variables I ever needed were PATH_INFO,
REQUEST_METHOD, QUERY_STRING and maybe one more, all of which should
be available from CGI, too.

Thanks.

[Michele Simionato]

On Jul 4, 2:49 pm, [e-mail] wrote:

Dear all,

what is the difference? Middleware?

Yes, and also the fact that you have a large choice of WSGI web
frameworks to choose
from. CGI looks so much 20th century ... ;)
Michele Simionato

[Josiah Carlson]

tu*********@gmail.com wrote:

I'm wondering because the only variables I ever needed were PATH_INFO,
REQUEST_METHOD, QUERY_STRING and maybe one more, all of which should
be available from CGI, too.

CGI starts up a new process for every request, using stdin/stdout for
passing information. I believe WSGI can do that, but I believe it can
also do in-process requests (think mod_python, only with a Python web
server), external process requests (think FastCGI or LRWP), etc.

I could certainly be mistaken, it's been a while since I looked into any
of it.

- Josiah

[Bruno Desthuilliers]

tu*********@gmail.com a écrit :

Dear all,

what is the difference? Middleware?

I'm wondering because the only variables I ever needed were PATH_INFO,
REQUEST_METHOD, QUERY_STRING and maybe one more, all of which should
be available from CGI, too.

Thanks.

WSGI is intented as a gateway between a web server and a long-running
python application. Which means you don't have to launch a new Python
interpreter, import libs, parse config, connect to the database etc etc
for each and every request.

Also, it's (IMHO) much more usable than CGI.