Skip to content
体验新版
项目
组织
正在加载...
登录
切换导航
打开侧边栏
张重言
rails
提交
c14c7982
R
rails
项目概览
张重言
/
rails
通知
1
Star
0
Fork
0
代码
文件
提交
分支
Tags
贡献者
分支图
Diff
Issue
0
列表
看板
标记
里程碑
合并请求
0
Wiki
0
Wiki
分析
仓库
DevOps
项目成员
Pages
R
rails
项目概览
项目概览
详情
发布
仓库
仓库
文件
提交
分支
标签
贡献者
分支图
比较
Issue
0
Issue
0
列表
看板
标记
里程碑
合并请求
0
合并请求
0
Pages
分析
分析
仓库分析
DevOps
Wiki
0
Wiki
成员
成员
收起侧边栏
关闭侧边栏
动态
分支图
创建新Issue
提交
Issue看板
体验新版 GitCode,发现更多精彩内容 >>
提交
c14c7982
编写于
8月 10, 2015
作者:
R
Rafael Mendonça França
浏览文件
操作
浏览文件
下载
差异文件
Merge pull request #21188 from derekprior/dp-asset-host-docs
Update info on browser connection limits [ci skip]
上级
8e014f28
0d8b552c
变更
1
隐藏空白更改
内联
并排
Showing
1 changed file
with
18 addition
and
11 deletion
+18
-11
actionview/lib/action_view/helpers/asset_url_helper.rb
actionview/lib/action_view/helpers/asset_url_helper.rb
+18
-11
未找到文件。
actionview/lib/action_view/helpers/asset_url_helper.rb
浏览文件 @
c14c7982
...
...
@@ -31,26 +31,33 @@ module Helpers
# stylesheet_link_tag("application")
# # => <link href="http://assets.example.com/assets/application.css" media="screen" rel="stylesheet" />
#
# Browsers
typically open at most two simul
taneous connections to a single
# host
, which means your assets often have to wait for other assets to finish
#
downloading. You can alleviate this by using a <tt>%d</tt> wildcard in the
#
+asset_host+. For example, "assets%d.example.com". If that wildcard is
#
present Rails distributes asset requests among the corresponding four hosts
#
"assets0.example.com", ..., "assets3.example.com". With this trick browsers
#
will open eight simultaneous connections rather than two
.
# Browsers
open a limited number of simula
taneous connections to a single
# host
. The exact number varies by browser and version. This limit may cause
#
some asset downloads to wait for previous assets to finish before they can
#
begin. You can use the <tt>%d</tt> wildcard in the +asset_host+ to
#
distribute the requests over four hosts. For example,
#
<tt>assets%d.example.com<tt> will spread the asset requests over
#
"assets0.example.com", ..., "assets3.example.com"
.
#
# image_tag("rails.png")
# # => <img alt="Rails" src="http://assets0.example.com/assets/rails.png" />
# stylesheet_link_tag("application")
# # => <link href="http://assets2.example.com/assets/application.css" media="screen" rel="stylesheet" />
#
# To do this, you can either setup four actual hosts, or you can use wildcard
# DNS to CNAME the wildcard to a single asset host. You can read more about
# setting up your DNS CNAME records from your ISP.
# This may improve the asset loading performance of your application.
# It is also possible the combination of additional connection overhead
# (DNS, SSL) and the overall browser connection limits may result in this
# solution being slower. You should be sure to measure your actual
# performance across targeted browers both before and after this change.
#
# To implement the corresponding hosts you can either setup four actual
# hosts or use wildcard DNS to CNAME the wilcard to a single asset host.
# You can read more about setting up your DNS CNAME records from your ISP.
#
# Note: This is purely a browser performance optimization and is not meant
# for server load balancing. See http://www.die.net/musings/page_load_time/
# for background.
# for background and http://www.browserscope.org/?category=network for
# connection limit data.
#
# Alternatively, you can exert more control over the asset host by setting
# +asset_host+ to a proc like this:
...
...
编辑
预览
Markdown
is supported
0%
请重试
或
添加新附件
.
添加附件
取消
You are about to add
0
people
to the discussion. Proceed with caution.
先完成此消息的编辑!
取消
想要评论请
注册
或
登录