diff options
| author | jam@chromium.org <jam@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2009-03-10 20:21:01 +0000 |
|---|---|---|
| committer | jam@chromium.org <jam@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2009-03-10 20:21:01 +0000 |
| commit | df8e6febb83b0b8897594abf24f1a38368732df9 (patch) | |
| tree | 57c1cf8278bd5cda887ecb3fe7e33013525bedea /tools/xcodebodge | |
| parent | 92ca623270d61b3f6574d4f721c5a7ba1ac64f1b (diff) | |
| download | chromium_src-df8e6febb83b0b8897594abf24f1a38368732df9.zip chromium_src-df8e6febb83b0b8897594abf24f1a38368732df9.tar.gz chromium_src-df8e6febb83b0b8897594abf24f1a38368732df9.tar.bz2 | |
Instead of queuing ResourceDispatcher IPC messages in RenderView, use ResourceDispatcherHost's ability to block requests for a given route in the browser process. This is in prepration for switching to one ResourceDispatcher in the renderer process, instead of one per RenderView, to share more code between child processes.
I realize that this means that resource requests for RenderViews created by other RenderViews will start a little bit later now (after a hop to the UI thread and back), but I don't think it should lead to much delay (since if our UI thread is that bogged down, we have bigger problems). I'll make sure this is the case by looking at the page cyclers.
Review URL: http://codereview.chromium.org/42005
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@11370 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'tools/xcodebodge')
0 files changed, 0 insertions, 0 deletions