diff options
author | backer@chromium.org <backer@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2011-02-08 22:45:22 +0000 |
---|---|---|
committer | backer@chromium.org <backer@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2011-02-08 22:45:22 +0000 |
commit | 5478c37c9b98c45a3a6f84ede2513938f9f25168 (patch) | |
tree | 332f2c3237fb43dc9159d72fa89eec9a7b2f7753 /net/base/ssl_connection_status_flags.h | |
parent | 5fc9d629f0302fffbf70673a54b31814e063c875 (diff) | |
download | chromium_src-5478c37c9b98c45a3a6f84ede2513938f9f25168.zip chromium_src-5478c37c9b98c45a3a6f84ede2513938f9f25168.tar.gz chromium_src-5478c37c9b98c45a3a6f84ede2513938f9f25168.tar.bz2 |
Move most of GpuProcessHost processing to GpuProcessHostUIShim.
This is a refactoring to support the browser using the GPU process for drawing. Currently most of the communication with the GPU process (via GpuProcessHost) happens on the IO thread (where requests come in from the renderer). In the future, the browser will be drawing from the UI thread. Rather than have two entry points (or a lot of explicit thread hopping), I've moved GpuMessageFilter (the proxy for the renderer) to the UI thread and most of GpuProcessHost functionality to GpuProcessHostUIShim.
This cleans up some of the CVCBThreadHopping mess from an earlier commit.
BUG=none
TEST=none
Review URL: http://codereview.chromium.org/6349079
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@74192 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'net/base/ssl_connection_status_flags.h')
0 files changed, 0 insertions, 0 deletions