> I would like to know about uWSGI . i haven't tried it yet. > > 1 - Is that a gateway to interface between other web servers ? > (Apache/Cherokee/nginx etc)
it depends, if you need a specific webserver front-end you can use it and connect to uWSGI via one of the supported protocols (oviously the uwsgi protocol is the suggested one). Normally, putting an application directly connected to the public network is not a good idea. So you will very probably ends always putting uWSGI behind some sort of "filter" (read: webserver/webrouter/loadbalancer) > 2 - It seems that can be use as a webserver alone but how it works. Is > that > reliable /Fast? again, it depends on your setup. If you put static assets on another host, you only need a "filter" before your app, and you can use the included http-router. It can manages thousand of HTTP requests (in non blocking way) and forward them to uWSGI nodes. This area is fastly evolving (like persistent connections support, sctp and automatic clustering management) and could be interesting from a "research" poin of view. Serving static files via uWSGI could be really fast if you have few concurrent connections, but it cannot reach nginx/cherokee performance on request storming (by default uWSGI concurrency is limited by the number of spawned threads/processes) > 3 - It was mentioned that The download/upload corruption do not happen in > uWSGI , how you use it? Stanalone or as an gateway/interface for other > webserver/reverse proxy? > If you want to follow the "solid path", use some rock-solid webserver (like nginx, cherokee or apache) forwarding requests to one (or more) uWSGI nodes. If you plan to have dozens of nodes with ultra scalability with no effort, try to follow the http-router development (even if you could need something like nginx/haproxy for managing https connections). -- Roberto De Ioris http://unbit.it
