[Page Load Metrics] PageLoadMetrics Mojofication.

chrome/renderer/page_load_metrics/metrics_render_frame_observer.cc

Index: chrome/renderer/page_load_metrics/metrics_render_frame_observer.cc
diff --git a/chrome/renderer/page_load_metrics/metrics_render_frame_observer.cc b/chrome/renderer/page_load_metrics/metrics_render_frame_observer.cc
index 059653cbaf9ebc27469efbaf6d40328aa3d5bb12..8622bae774639a59fe6067bd11afe646d3eca495 100644
--- a/chrome/renderer/page_load_metrics/metrics_render_frame_observer.cc
+++ b/chrome/renderer/page_load_metrics/metrics_render_frame_observer.cc
@@ -12,6 +12,7 @@
 #include "chrome/renderer/page_load_metrics/page_timing_metrics_sender.h"
 #include "chrome/renderer/page_load_metrics/renderer_page_track_decider.h"
 #include "chrome/renderer/searchbox/search_bouncer.h"
+#include "content/public/common/associated_interface_provider.h"
 #include "content/public/renderer/render_frame.h"
 #include "third_party/WebKit/public/web/WebDataSource.h"
 #include "third_party/WebKit/public/web/WebDocument.h"
@@ -37,6 +38,17 @@ MetricsRenderFrameObserver::MetricsRenderFrameObserver(
 
 MetricsRenderFrameObserver::~MetricsRenderFrameObserver() {}
 
+void MetricsRenderFrameObserver::SendTiming(const PageLoadTiming& timing,
+                                            const PageLoadMetadata& metadata) {
+  if (HasNoRenderFrame())
+    return;
+  if (!page_load_metrics_) {
+    render_frame()->GetRemoteAssociatedInterfaces()->GetInterface(
+        &page_load_metrics_);
+  }
+  page_load_metrics_->UpdateTiming(timing, metadata);

[Zhen Wang, 2017/04/19 18:49:54]

Why should MetricsRenderFrameObserver care about sending the data? I think this
should still be done by PageTimingMetricsSender.

Ideally, MetricsRenderFrameObserver does not need to worry about whether it is
using old IPC or mojo. PageTimingMetricsSender will take care of it.

[lpy, 2017/04/19 21:05:05]

MetricsRenderFrameObserver is IPC::Sender, PageTimingMetricsSender only batches
page timing, and call MetricsRenderFrameObserver itself to send the timing over
IPC. I maintain this logic here by making MetricsRenderFrameObserver to
implement a PageTimingSender API.

And as it turns out, this is easier to test/verify by separating the logic of
sending and batching. If PageTimingMetricsSender is doing the actually sending,
we need to fake a sender in MetricsRenderFrameObserver test, and intercept the
creation of the sender. See Patch Set #13 in the prototype CL as an example:
https://codereview.chromium.org/2731583002/#ps380001

In my opinion, the name of PageTimingMetricsSender is misleading, as it only
batches the timing and calls IPC::Sender to send the timing.

[Zhen Wang, 2017/04/19 21:52:47]

Oh, I see.

+}
+
 void MetricsRenderFrameObserver::DidChangePerformanceTiming() {
   // Only track timing metrics for main frames.
   if (IsMainFrame())
@@ -78,8 +90,8 @@ void MetricsRenderFrameObserver::DidCommitProvisionalLoad(
       timing = GetTiming();
       DCHECK(!timing.navigation_start.is_null());
     }
-    page_timing_metrics_sender_.reset(
-        new PageTimingMetricsSender(this, routing_id(), CreateTimer(), timing));
+    page_timing_metrics_sender_.reset(new PageTimingMetricsSender(
+        this, routing_id(), this, CreateTimer(), timing));
   }
 }