6 ms·
I'm not familiar with what you're talking about. Could you clarify something for me? Why would you need Nginx and twisted.web? Wouldn't you just call your WS
by tome 17y ago
I'm not familiar with what you're talking about. Could you clarify something for me? Why would you need Nginx and twisted.web? Wouldn't you just call your WSGI application from Nginx?
- jaddison 17y agoNginx's architecture doesn't really mesh well with WSGI's interface protocol... I believe it has to do with blocking the serving Nginx process whilst the WSGI request is being processed. Nginx prefers to "pass off" the request to a web-app server to do the heavy lifting and take care of fast, easy serving in the fastest way possible.
- tome 17y agoThanks!
- blasdel 17y agoBecause it's preferable to always use real HTTP between independent processes at every layer boundary
- tome 17y agoI don't understand that reasoning. If you've got to got to WSGI at some point anyway, why not straight away?