Browser performance improvement in RubyOnRails
From changelog:
Work around the two connection per host browser limit: use asset%d.myapp.com to distribute asset requests among asset[0123].myapp.com. Use a DNS wildcard or CNAMEs to map these hosts to your asset server. See http://www.die.net/musings/page_load_time/ for background.
Before that change rails allows only one asserts domain.
Added X-Runtime to all responses with the request run time [DHH] (rename from X-Benchmark)
On Firefox you can use WebDeveloper or Firebug extensions to see that header.
Another nice thing (ETag) desribed by Chad Fowler - Edge Rails Goody: Automatic 304 for Views Not Modified
Work around the two connection per host browser limit: use asset%d.myapp.com to distribute asset requests among asset[0123].myapp.com. Use a DNS wildcard or CNAMEs to map these hosts to your asset server. See http://www.die.net/musings/page_load_time/ for background.
Before that change rails allows only one asserts domain.
Added X-Runtime to all responses with the request run time [DHH] (rename from X-Benchmark)
On Firefox you can use WebDeveloper or Firebug extensions to see that header.
Another nice thing (ETag) desribed by Chad Fowler - Edge Rails Goody: Automatic 304 for Views Not Modified
Автор: Sergey в
2:08 PM
Комментарии: 0:
Отправить комментарий
Подпишитесь на каналы Комментарии к сообщению [Atom]
<< Главная страница