> > Argh, no, this is not required, it is only a (crazy, as the title) example > on how to maintain a WSGI style approach. You can always send raw data to > the communication socket (even if it is considered blasphemous by the WSGI > crew.... :P) via the uwsgi api. >
OK. I would like to see this and hopefully it will work well. > Let's clarify things as this is taking to form of a flame :) > > I do not love WSGI, i am pretty sure the vast majority of people (even in > WEB-SIG) do not like it, and are demanding for a new approach. But it is > here, all of the python web frameworks use it. We have to live with it :) > > If a user can/want to use Brubeck it will probably be able to use mongrel2 > at its max, all of the others still need to rely on solutions like uWSGI > or wsgid. I would like to see a future without WSGI and I'm building Brubeck to help invent that future. WSGI needs to go away. I'd also like to say that uWSGI is a very confusing name for a project that doesn't seem to require WSGI.
