diff options
author | rch@chromium.org <rch@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2012-06-04 23:49:55 +0000 |
---|---|---|
committer | rch@chromium.org <rch@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2012-06-04 23:49:55 +0000 |
commit | 0d734542e6665805e613129d91000a5d83b42929 (patch) | |
tree | bbd624add983d56dca9c1d61cdada0859e8d042a /chrome/browser/chromeos/cros/network_library_unittest.cc | |
parent | 2544cbb6491bd95c76e477b8777496c966c7db9d (diff) | |
download | chromium_src-0d734542e6665805e613129d91000a5d83b42929.zip chromium_src-0d734542e6665805e613129d91000a5d83b42929.tar.gz chromium_src-0d734542e6665805e613129d91000a5d83b42929.tar.bz2 |
Increase Chrome SPDY/3 stream receive window to 10MB. The goal is to set the SPDY window high enough that we'd never realistically hit it, since we'd hit TCP flow control first. The buffers are kept in the Chrome browser process, which should ship things over to WebKit immediately, so the buffers should almost always be small, unless the renderer process goes out to lunch or we're getting a ton of server pushed stuff (unless it goes to browser cache, but I don't think we do that yet, but I forget). 10MB per stream prevents us from completely hosing the browser process in these exceptional situations
Change SpdySession so that if the initial receive window size is larger than
the protocol default, notify the server.
Rename SendSettings to SendInitialSettings to be more clear.
BUG=131055
TEST=SpdySessionSpdy3Test.SendInitialWindowSizeSettingsOnNewSession
Review URL: https://chromiumcodereview.appspot.com/10479014
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@140433 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'chrome/browser/chromeos/cros/network_library_unittest.cc')
0 files changed, 0 insertions, 0 deletions