On 14, April 2010, at 14 Apr 10:33, Clifford Heath wrote: > I assume then that browsers don't pipeline requests? > A pity, because sending twenty requests up one or two > sockets and streaming all the responses down should be > faster than anything else.
Most browsers will only send 2 requests at a time, per host. One simple way around it if you are on a budget and your traffic is not high is to use multiple DNS entries for the same server. Then you can use the asset host options in rails out of the box and the only modification you need to make is add the aliases on your web server. Even just having a separate domain name for img.domain, css.domain, js.domain and www.domain can be used if you are just running something like static or sinatra apps. This can seriously reduce page load time (from experience). Mikel -- You received this message because you are subscribed to the Google Groups "Ruby or Rails Oceania" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rails-oceania?hl=en.
