In case you didnt read the previous post in the thread my email was in reguards to apache traffic server and not in reguards to nginx (I know it doesnt not support HTTP/1.1) I am looking for a intermediary between the two to use to reduce round packet trips/delay.<br>
<br>Candidates so far:<br>ViCompress (has connection pool support, C, event based), PerlBal (has connection pool support, Perl, event based), Apache Traffic Server (connection pool support???, C?, event based)<br><br>Of course it would be preferable that nginx have HTTP/1.1 support but I dont see that happening soon.<br>
<br><br><div class="gmail_quote">On Tue, Oct 26, 2010 at 1:51 PM, Weibin Yao <span dir="ltr"><<a href="mailto:nbubingo@gmail.com">nbubingo@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">SplitIce at 2010-10-26 10:44 wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Indeed I found that in my research but I cant find any real documentation on its keep alive system/backend pooling. This leads me to beleive it just fowards the keep alive onto the backend server, which is not preferable. Any ideas?<br>
</blockquote></div>
No，it's not supported yet.<br>
<br>
-- <br><font color="#888888">
Weibin Yao</font><div><div></div><div class="h5"><br>
<br>
<br>
_______________________________________________<br>
nginx mailing list<br>
<a href="mailto:nginx@nginx.org" target="_blank">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>