summaryrefslogtreecommitdiffstats
path: root/app/surface/accelerated_surface_mac.h
diff options
context:
space:
mode:
authorgavinp@chromium.org <gavinp@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2011-01-27 15:51:34 +0000
committergavinp@chromium.org <gavinp@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2011-01-27 15:51:34 +0000
commit82aed06f371ff5938ad848ff4511d81d82418bee (patch)
treeffac6946a7b271e1419df35b4297d30ec2ed9be9 /app/surface/accelerated_surface_mac.h
parent665acb177ed2c3ce59ec2c1f70597856eebeae45 (diff)
downloadchromium_src-82aed06f371ff5938ad848ff4511d81d82418bee.zip
chromium_src-82aed06f371ff5938ad848ff4511d81d82418bee.tar.gz
chromium_src-82aed06f371ff5938ad848ff4511d81d82418bee.tar.bz2
Add histogram for HTTP response codes
This adds an histogram to the HTTP response header parser. I reviewed the code, and I've convinced myself that this captures the two main cases of HTTP header parsing (tunneling, and normal HTTP), and that double-calls aren't occuring. I liked having all the code in the one translation unit. But, I might have missed one, and we might still be getting called twice for the same load: so the statistics might be off. Alternatively, I could put a static function on HttpResponseHeader, to be called from the site of parse. But this might miss a parse. All in all, I wanted to be sure to catch all distinct response codes we get, so we can be sure not to stomp on anything. So I chose the approach using the HttpResponseHeaders constructor. TEST=none BUG=70428 Review URL: http://codereview.chromium.org/6317011 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@72801 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'app/surface/accelerated_surface_mac.h')
0 files changed, 0 insertions, 0 deletions