> > > > > ________________________________ > > >>I can give it a try adding a 'puwsgi' protocol handler. Take in account >> that async mode with persistent connections is broken, so you have to >> relay >>on threads and processes. > > > Can you clarify what you mean by "async mode with persistent connections > is broken"? > > I understand that right now uWSGI does not support persistent connection > but that feature can be added, right?
right Are you also saying that even if you > add persistent connection to uWSGI it still won't work with async/gevent? > If so, is there any fundamental reason why async doesn't work with > persistent connection? because the current async.c code stop to process events after it receives a full uwsgi/fastcgi/http message. All the following bytes will be directly read by the application itself (via wsgi.input/rack.input/psgi.input and so on). It should be updated to re-add the socket to the event queue. Could be easy, but it requires a lot of testing infrastructure as the async mode is the base for 6 plugins (gevent included) -- Roberto De Ioris http://unbit.it _______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
