> > >>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) > > Ah I see... so any plan of implementing that? It'd be cool > :)_______________________________________________ >
I would like to make some benchmark first. If maintaining connection open will gain 0.1% performance i would prefer to concentrate on something else :) -- Roberto De Ioris http://unbit.it _______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
