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>
<br><div class="gmail_quote">On Tue, Oct 26, 2010 at 3:57 AM, Ryan Malayter <span dir="ltr"><<a href="mailto:malayter@gmail.com">malayter@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><div></div><div class="h5">On Mon, Oct 25, 2010 at 1:01 AM, SplitIce <<a href="mailto:mat999@gmail.com">mat999@gmail.com</a>> wrote:<br>
> Has anyone here had any luck using a 2 layer proxy system to provide<br>
> keep-alive support to nignx's backend.<br>
><br>
> My goal is to setup a system like thihi<br>
> User -> Nginx -> SoftwareX -> Backend (Different Country) -> SoftwareX -><br>
> Nginx ->User<br>
> So in other words another layer.<br>
><br>
> Ive done some research and found perlbal and vicompress. Any other software<br>
> that supports a HTTP/1.1 backend pool (keep alive) that you know of? Any<br>
> recomendations?<br>
><br>
> Oh and BTW to anyone who says that it wont matter, it will, it will remove<br>
> the need for a round trip in the proxy process (19ms), big saving.<br>
><br>
</div></div>I think Apache Traffic Server may do what you need:<br>
<a href="http://trafficserver.apache.org/" target="_blank">http://trafficserver.apache.org/</a><br>
<font color="#888888"><br>
--<br>
RPM<br>
<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>
</font></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>