> > > everyone is over double - then do it the right way and cut WSGI out > > completely. > > > > sorry, i do not know wich kind of benchmark you have made, but for an > hello world mongrel2+uWSGI outperform mongrel2+brubeck in every test. >
I'd like to see this backed with data. Remember uWSGI it is a pure-c app, it only goes into python for the > "return Hello World" part (even start_response is implemented in pure-c). > What do you think Brubeck is doing? > I do not want to start a flame, but honestly i do no understand what is > your problem with my announcement, uWSGI is out by years and already used > in a lot of context, why having it supporting mongrel2 should be a problem > instead of a good thing ? > I'm not saying it's a problem. I was suggesting a path that does not use WSGI and doesn't lead to confusing code. WSGI is not async without special work and that work puts you back in Python, so your claim about pure-c makes no sense. On top of that, uWSGI's async layer is a confusing mess. You have implicit AND explicit context switching in the same project! Alas, I didn't mean to offend. Only inform. There is a LOT of misunderstanding around async in Python.
