<div>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">Browsers will only make a limited number of HTTP connections to a<br>specific host. By using multiple hostnames, you increase the number of
<br>concurrent connections a browser will make. It is also useful to<br>seperate static content from dynamic content because dynamic content<br>servers typically are heavy weight (Apache w/mod_perl or mod_php)<br>compared to static content servers (lighttpd, nginx, etc).
<br></blockquote></div>
<div>I didn't know about the limited connections per host. Thanks!</div>
<div> </div>
<div>Regarding separating static and dynamic content servers, doesn't PerlBal pretty much act as the go-between? </div>
<div> </div>
<div>Perlbal gets a request for <a href="http://www.site.com/1.jpg">www.site.com/1.jpg</a>, it passes the request to the PHP server. The PHP server talks to MogileFS tracker and the tracker lets the PHP server know the real file location is in
<a href="http://whatever.site.com/abc.fid">whatever.site.com/abc.fid</a>. It then sends a reproxy header to PerlBal, and PerlBal fetches the actual file from <a href="http://whatever.site.com/abc.fid">whatever.site.com/abc.fid
</a> (which happens to run lighttpd) and returns it to the client.<br> </div>
<div>Thus this would still allow separation of dynamic vs. static content doesn't it?</div>
<div> </div>