Any chance you'd care to help someone understand how WSGI differs from CGI? Does WSGI work on any run of the mill 9.99/mo web hoster? Does WSGI have better performance, and why? If CGI is "considered harmful" I'd certainly like to make the switch. Any advice?

-Greg
Greg | Homepage | 06/10/08 - 8:17 pm | #

WSGI is a protocol to allow components of a web stack to communicate. My understanding is that in order to use it, you will need a server that 'speaks' WSGI. (mod_wsgi anyone ?)

If your app *runs* as a CGI, then I doubt you can use it, unless your app communicates with other components: in which case I guess you could use at least parts of WSGI for that.
Fuzzyman | Homepage | 06/10/09 - 3:52 pm | #

WSGI is purely an in-process communication standard. So it doesn't invalidate CGI particularly. You can still write CGI scripts (perhaps using the CGI WSGI server in the PEP 333 spec), and you won't box yourself into CGI later if you want to change your environment. (Though it's not magical; if you do CGI-like things where you expect the process to live for only one process then it won't work for you).
Ian Bicking | Homepage | 06/10/09 - 4:21 pm | #