[net] Change order of RequestPriority to natural: higher > lower

net/base/prioritized_dispatcher.h

Index: net/base/prioritized_dispatcher.h
diff --git a/net/base/prioritized_dispatcher.h b/net/base/prioritized_dispatcher.h
index c10061bbc02cbcb3dd5ef3e37bd7c2b989a3e1c4..446ddaa2762fe4a02bf9f60361b8424ab469046c 100644
--- a/net/base/prioritized_dispatcher.h
+++ b/net/base/prioritized_dispatcher.h
@@ -13,7 +13,7 @@
 
 namespace net {
 
-// A priority-based dispatcher of jobs. Dispatch order is by priority (lowest
+// A priority-based dispatcher of jobs. Dispatch order is by priority (highest

[Ryan Hamilton, 2012/04/23 22:51:05]

I didn't expect to see a comment change in a consumer.  Was the old comment
incorrect, or is there a change in functionality?  (I think the former)

[szym, 2012/04/24 00:19:31]

The old comment was misleading and a source of confusion both in the original
review (eroman@) and the readability review (stevez@). The functionality is the
same. 

 // first) and then FIFO. The dispatcher enforces limits on the number of running
 // jobs. It never revokes a job once started. The job must call OnJobFinished
 // once it finishes in order to dispatch further jobs.
@@ -32,7 +32,7 @@ class NET_EXPORT_PRIVATE PrioritizedDispatcher {
   // For example, |total_jobs| = 30 and |reserved_slots| = { 5, 10, 5 }
   // allow for at most 30 running jobs in total. If there are already 24 jobs
   // running, then there can be 6 more jobs started of which at most 1 can be
-  // at priority 1 or 0, but the rest has to be at 0.
+  // at priority 1 or 2, but the rest has to be at 2.

[Ryan Hamilton, 2012/04/23 22:51:05]

nit: "the rest have to be" (instead of has)

   struct NET_EXPORT_PRIVATE Limits {
     Limits(Priority num_priorities, size_t total_jobs);
     ~Limits();