> > Well, I was mostly thinking if/whether uWSGI's power/advantage is > becoming more obvious when serving big web sites with *LOT* of traffic > where one wants to squueze last drop of performance.
The problem is that when you are just learning, the first objective is getting things done, you are generally not interested in problems you do not even immagine will arise (soon or later) This is why projects like uWSGI, Passenger or the big J2EE application servers seems "overpowered" to beginners (or to super-lucky people that never had problems with webapps :) It is not (only) a matter of performance, from a sysadmin point of view things are different, that is why i removed "developer-friendly" from the uWSGI front-page :P > > > python anyserver.py -p localport -s gunicorn > wait wait, you are talking about anyserver.py, it is a cool script included in web2py for simplified deployments, you cannot really say you have tried gunicorn and its true power :) regarding the https problem, well, if the password file is correct it should works transparently (uWSGI honour the X-Forwarded-SSL header sent by the webfaction proxy). -- Roberto De Ioris http://unbit.it -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
