Has anyone here had any luck using a 2 layer proxy system to provide
keep-alive support to nignx’s backend.
My goal is to setup a system like this:
User -> Nginx -> SoftwareX -> Backend (Different Country) -> SoftwareX
->
Nginx ->User
So in other words another layer.
Ive done some research and found perlbal and vicompress. Any other
software
that supports a HTTP/1.1 backend pool (keep alive) that you know of? Any
recomendations?
Oh and BTW to anyone who says that it wont matter, it will, it will
remove
the need for a round trip in the proxy process (19ms), big saving.
On Mon, Oct 25, 2010 at 1:01 AM, SplitIce [email protected] wrote:
recomendations?
Oh and BTW to anyone who says that it wont matter, it will, it will remove
the need for a round trip in the proxy process (19ms), big saving.
I think Apache Traffic Server may do what you need:
http://trafficserver.apache.org/
–
RPM
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?
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.
Candidates so far:
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)
Of course it would be preferable that nginx have HTTP/1.1 support but I
dont
see that happening soon.
SplitIce at 2010-10-26 10:44 wrote:
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?
No，it’s not supported yet.
–
Weibin Y.