Enabled actual transfer size in chromium

content/browser/renderer_host/async_resource_handler.cc

Index: content/browser/renderer_host/async_resource_handler.cc
diff --git a/content/browser/renderer_host/async_resource_handler.cc b/content/browser/renderer_host/async_resource_handler.cc
index 4e80081e8ea1cb972d1707c22c2c5543cffaf91d..480b674a3225cb7432ac85540dae57df39ffbfdf 100644
--- a/content/browser/renderer_host/async_resource_handler.cc
+++ b/content/browser/renderer_host/async_resource_handler.cc
@@ -216,8 +216,11 @@ bool AsyncResourceHandler::OnReadCompleted(int request_id, int* bytes_read) {
   // We just unmapped the memory.
   read_buffer_ = NULL;
 
+  net::URLRequest* request = rdh_->GetURLRequest(
+      GlobalRequestID(filter_->child_id(), request_id));
+  int bytes_received = DevToolsNetLogObserver::GetAndResetTransferSize(request);

[darin (slow to review), 2011/04/05 19:02:18]

nit: it feels like there is too much different terminology going on here.

we have "Get*TransferSize", "bytes_received", and at the WebKit API
"lengthReceived".  these all mean the same thing.  one term would be better than
three :)

[vsevik, 2011/04/07 16:32:49]

As discussed, everything with this meaning is renamed to raw_data_length.

   filter_->Send(new ResourceMsg_DataReceived(
-      routing_id_, request_id, handle, *bytes_read));
+      routing_id_, request_id, handle, *bytes_read, bytes_received));
 
   return true;
 }