Talking direct to uwsgi requires a python helper as Graham mentions. While I do like the nginx/uwsgi stack, I don't have any problems with apache/mod_wsgi. Both are very capable and I find that apache/ mod_wsgi is probably easier to set up and has a much larger support/ installed base. I've deployed applications using both. In terms of stability, neither architecture has had any real issues. In terms of performance, nginx has a large edge on static files and for this particular project, that was necessary. I haven't found the server -> wsgi -> pylons gateway to be significantly better or worse in either scenario.
http://www.reddit.com/r/Python/comments/be1q1/benchmark_of_python_web_servers/ is a discussion of the benchmark site listed above with quite a venomous discussion. As a personal recommendation, I typically would push someone in the Apache/mod_wsgi direction, but, there are reasons to chose competing solutions based on the full stack management. While it may add somewhat to the support burden, choosing a solution that isn't widely deployed will sometimes cause issues. -- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en.
