Could somebody give me a high-level technical overview of WSGI details behind the scenes vs other we
Posted
by orokusaki
on Stack Overflow
See other posts from Stack Overflow
or by orokusaki
Published on 2010-04-29T18:43:20Z
Indexed on
2010/04/29
18:47 UTC
Read the original article
Hit count: 528
Firstly:
- I understand what WSGI is and how to use it
- I understand what "other" methods (Apache mod-python, fcgi, et al) are, and how to use them
- I understand their practical differences
What I don't understand is how each of the various "other" methods work compared to something like UWSGI, behind the scenes. Does your server (Nginx, etc) route the request to your WSGI application and UWSGI creates a new Python interpreter for each request routed to it? How much different is is from the other more traditional / monkey patched methods is WSGI (aside from the different, easier Python interface that WSGI offers)? What light bulb moment am I missing?
© Stack Overflow or respective owner
