If you do implement a HTTP/1.1 backend support module me and alot of people will love you.<br><br><div class="gmail_quote">On Tue, Nov 23, 2010 at 6:18 PM, agentzh <span dir="ltr"><<a href="mailto:agentzh@gmail.com">agentzh@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div class="im">On Tue, Nov 23, 2010 at 5:44 AM, John Axel Eriksson <<a href="mailto:john@insane.se">john@insane.se</a>> wrote:<br>
> Thanks so much for replying! I'm very very saddened though since I love nginx so much but<br>
> now must part ways.<br>
<br>
</div>We do really want this feature as well. We're now using ngx_proxy as a<br>
non-blocking HTTP client for our ngx_lua applications (we also use<br>
ngx_drizzle as the non-blocking mysql client and ngx_memc for the<br>
memcached/tokyotyrant).<br>
<div class="im"><br>
> Is there any sort of plan to support this in the future? I guess it might mean<br>
> you must support http 1.1 to backends...<br>
><br>
<br>
</div>Our team will try implementing ngx_proxy_more or something like that<br>
to include basic HTTP 1.1 (keepalive + chunked) support to ngx_proxy<br>
in the first quarter of the next year if Igor does not do that himself<br>
already.<br>
<br>
Cheers,<br>
<font color="#888888">-agentzh<br>
</font><div><div></div><div class="h5"><br>
_______________________________________________<br>
nginx mailing list<br>
<a href="mailto:nginx@nginx.org">nginx@nginx.org</a><br>
<a href="http://nginx.org/mailman/listinfo/nginx" target="_blank">http://nginx.org/mailman/listinfo/nginx</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br><a href="http://thewarezscene.org" target="_blank">Warez Scene</a> <a href="http://www.nexusddl.com" target="_blank">Free Rapidshare Downloads</a><br><br>