> On 2014-02-27 17:53, Roberto De Ioris wrote:
>
>> The http-socket does not support keep-alives (as it is meant to be run
>> behind a proxy)
>
> Does it mean that there is no plan to add this support in the future?
>
> Best regards,
> /Alexander
>
> _______________________________________________
> uWSGI mailing list
> [email protected]
> http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
>
we discussed it a lot, and for proper keep alive you need to parse each
response. The cost (complexity) of it, compared to the little gain when
the backend is local (or even lan) it is not whorty.
A different thing is the persistent-uwsgi support added in 2.0. It is
meant for rpc where every microsecond is vital.
So no, currently there is no plan for it.
Having said that there are other approaches on work/study, like blindly
trusting the headers generated by the app:
# pseudo code
if 'Keep-Alive' in response_headers:
do_not_close_socket_and_wait_for_the_next_chunk()
teoretically it should work (if you know what you are doing)
--
Roberto De Ioris
http://unbit.it
_______________________________________________
uWSGI mailing list
[email protected]
http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
