What about using something like nginx instead of Apache as a proxy to multiple images? Has anyone used nginx ?<br><br><a href="http://nginx.net/">http://nginx.net/</a><br><br>Bob<br><br><div class="gmail_quote">On Fri, Apr 4, 2008 at 6:14 AM, Bert Freudenberg <<a href="mailto:bert@freudenbergs.de">bert@freudenbergs.de</a>> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div><div></div><div class="Wj3C7c"><br>
On 04.04.2008, at 08:42, Avi Bryant wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
On Thu, Apr 3, 2008 at 7:25 PM, Andreas Raab <<a href="mailto:andreas.raab@gmx.de" target="_blank">andreas.raab@gmx.de</a>> wrote:<br>
<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
We currently don't do this mostly because I'm unaware of a low-latency<br>
proxy/forwarding solution that we could use (obviously we're more concerned<br>
about latency than most web-based services). What do you use to redirect the<br>
incoming connections?<br>
</blockquote>
<br>
We use Apache with mod_proxy. This is fine for HTTP (the extra<br>
latency literally gets lost in the noise), but a chattier protocol<br>
would be different, of course. I wonder if someone who knew their way<br>
around ipfw could rig something up...<br>
</blockquote>
<br>
<br></div></div>
Yes, iptables magic came to my mind, too. This would have very low latency overhead, I doubt it would be measurable at all.<br><font color="#888888">
<br>
- Bert -<br>
<br>
<br>
<br>
</font></blockquote></div><br>