diff options
| author | willchan@chromium.org <willchan@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2011-11-30 04:57:26 +0000 |
|---|---|---|
| committer | willchan@chromium.org <willchan@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2011-11-30 04:57:26 +0000 |
| commit | cb8a5468be6eb5072a8e9173b554448c0d06e111 (patch) | |
| tree | abeebf8ce317ef7a728d54adf3ddba342f98acd1 /dbus/bus.h | |
| parent | 947be23b065106512e86df8795ccdc7c2cdd0afa (diff) | |
| download | chromium_src-cb8a5468be6eb5072a8e9173b554448c0d06e111.zip chromium_src-cb8a5468be6eb5072a8e9173b554448c0d06e111.tar.gz chromium_src-cb8a5468be6eb5072a8e9173b554448c0d06e111.tar.bz2 | |
Close idle connections / SPDY sessions when needed.
Due to the idle connection state being held by different socket pools, it's possible for one socket pool to hold an idle socket in a lower layer socket pool. From the lower level socket pool's perspective, the socket is being "actively" used. From the higher socket pool's (including SpdySession, which is more of a connection manager) perspective, the connection is idle and can be closed if we have hit a limit.
Normally this isn't a big deal, except when we have a lot of idle SPDY connections and are connecting via a proxy, so we have low connection limits through the proxy server. We address this problem by allowing lower-level socket pools to tell higher level socket pools to close a socket.
BUG=62364,92244
TEST=none
Review URL: http://codereview.chromium.org/8340012
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@112130 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'dbus/bus.h')
0 files changed, 0 insertions, 0 deletions