diff options
| author | simonjam@chromium.org <simonjam@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2011-12-01 22:20:06 +0000 |
|---|---|---|
| committer | simonjam@chromium.org <simonjam@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2011-12-01 22:20:06 +0000 |
| commit | 4b9f729a0b70ef2d916e718e48e9552dcc3d3e7d (patch) | |
| tree | b413ca358feda9c6a7799634163a61e9ac65ee56 /ui/base | |
| parent | 9d977272049fc90034052f0e0a930584a0a42e84 (diff) | |
| download | chromium_src-4b9f729a0b70ef2d916e718e48e9552dcc3d3e7d.zip chromium_src-4b9f729a0b70ef2d916e718e48e9552dcc3d3e7d.tar.gz chromium_src-4b9f729a0b70ef2d916e718e48e9552dcc3d3e7d.tar.bz2 | |
Slow start pipelining.
We need to wait for an HTTP/1.1 keep-alive response before we try to pipeline. Notably, this fixes wordpress.com and techcrunch.com.
Remember which hosts clearly support, or don't support pipelining. If pipelining is supported, skip the slow start. If it's not, fall back to HttpBasicStreams.
A site is judged not to support pipelining if we see an old HTTP version or encounter a socket error. A site does support pipelining if it successfully handles 3 requests. There's obviously room for improvement here, but this is a
start.
Related changes:
- In the spirit of CHECK() failing. Use CHECK(false) instead of NOTREACHED().
- HttpPipelinedHost is now an interface with a corresponding Impl. This is to help unit test HttpPipelinedHostPool.
BUG=None
TEST=net_unittests
Review URL: http://codereview.chromium.org/8586015
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@112557 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'ui/base')
0 files changed, 0 insertions, 0 deletions