diff options
| author | ttuttle <ttuttle@chromium.org> | 2015-04-28 09:17:47 -0700 |
|---|---|---|
| committer | Commit bot <commit-bot@chromium.org> | 2015-04-28 16:18:24 +0000 |
| commit | 1f2d7e9e15aee462a5e80c703f6a7d4886e23c25 (patch) | |
| tree | 5fc62eba6de448a7ced34f3aa9160792ad878a21 /gpu/gpu_common.gypi | |
| parent | 58b00a59bff3c44ef6e41f77d2afba4408f4564a (diff) | |
| download | chromium_src-1f2d7e9e15aee462a5e80c703f6a7d4886e23c25.zip chromium_src-1f2d7e9e15aee462a5e80c703f6a7d4886e23c25.tar.gz chromium_src-1f2d7e9e15aee462a5e80c703f6a7d4886e23c25.tar.bz2 | |
Plumb connection attempts from (non-proxy) ConnectJobs to HttpNetworkTransaction.
Log connection attempts in {Transport,SSL}ConnectJob and copy them into the ClientSocketHandle. Form there, copy them up the stack through the HttpStreamRequest (on job completion) to the HttpNetworkTransaction (on stream creation or failure).
SPDY is covered by this change -- sockets for new SPDY sessions are connected on the same path as sockets for HTTP connections, and then passed off to the SPDY code.
QUIC is not covered by this change -- sockets for new QUIC sessions are created in the QUIC code, and Chrome's current QUIC behavior does not let us see those results easily. My current plan is to log those *in* the QUIC code and then grab them on the next request that would use that QUIC session. I still need to see if this is actually practical.
BUG=480565
Review URL: https://codereview.chromium.org/1006643002
Cr-Commit-Position: refs/heads/master@{#327298}
Diffstat (limited to 'gpu/gpu_common.gypi')
0 files changed, 0 insertions, 0 deletions