Update network priorities to support better granularity

of resource loading from WebKit into the network stack.

In order to fully make these work, webkit changes are needed
as well.

BUG=none
TEST=none

Review URL: http://codereview.chromium.org/452033

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@33546 0039d316-1c4b-4281-b951-d872f2087c98

1 files changed, 13 insertions, 4 deletions

diff --git a/chrome/browser/renderer_host/resource_dispatcher_host.cc b/chrome/browser/renderer_host/resource_dispatcher_host.cc
index 036d907..89d13bb 100644
--- a/chrome/browser/renderer_host/resource_dispatcher_host.cc
+++ b/chrome/browser/renderer_host/resource_dispatcher_host.cc
@@ -533,11 +533,20 @@ void ResourceDispatcherHost::BeginRequest(
     // If the request is for the top level page or a frame/iframe, then we
     // should prioritize it higher than other resource types.  Currently, we
     // just use priorities 1 and 0.
-    if (request_data.resource_type == ResourceType::MAIN_FRAME ||
-        request_data.resource_type == ResourceType::SUB_FRAME) {
-      request->set_priority(1);
+    if (ResourceType::IsFrame(request_data.resource_type)) {
+      request->set_priority(net::HIGHEST);
     } else {
-      request->set_priority(0);
+      switch (request_data.resource_type) {
+        case ResourceType::STYLESHEET:
+        case ResourceType::SCRIPT:
+          request->set_priority(net::MEDIUM);
+          break;
+        case ResourceType::IMAGE:
+          request->set_priority(net::LOWEST);
+          break;
+        default:
+          request->set_priority(net::LOW);
+      }
     }
   }