> I'm not sure I understand what the advantage of wsgi would be, in any case > if somebody finds it useful here is the part of my nginx.conf with which I > run web2py with https access on a remote server; if somebody could post > instructions on running web2py through wsgi on nginx I would like to test > the difference.
It is uwsgi not wsgi. It is a network protocol for fast transfer of information (mainly string dictionary). It is binary based and very easy to parse (for a machine not for a human ;) ): http://projects.unbit.it/uwsgi/wiki/uwsgiProtocol You can think about it as "simplified fastcgi/scgi", even if uwsgi is not (only) related to cgi/http messages. Then there is the uWSGI project (that uses the uwsgi protocol) that is a web application container (it was born as a WSGI only server, but over time it has evolved a lot, supporting other languages). It includes all you can expect from a deploy platform (failover, automatic respawning, process monitoring, inter-cluster communications, resource limiting, logging...). You can find web2py configuration example here: http://projects.unbit.it/uwsgi/wiki/Example#Web2Py2uWSGI Handlers for the uwsgi protocol are available even for Cherokee (included in the official distribution), Apache2 (as external module) and lighttpd (external, not very well tested, module) I hope it can be useful -- Roberto De Ioris http://unbit.it
