Migrate components/data_reduction_proxy to Mojo interfaces.

chrome/common/chrome_content_client.cc

Index: chrome/common/chrome_content_client.cc
diff --git a/chrome/common/chrome_content_client.cc b/chrome/common/chrome_content_client.cc
index f4414936e8e0e89a3495aec4073693e75ea35484..6e398576de8c901493336452c9e270f56ba9e8a9 100644
--- a/chrome/common/chrome_content_client.cc
+++ b/chrome/common/chrome_content_client.cc
@@ -13,6 +13,7 @@
 #include "base/debug/crash_logging.h"
 #include "base/files/file_util.h"
 #include "base/json/json_reader.h"
+#include "base/memory/ptr_util.h"

[Anand Mistry (off Chromium), 2016/06/24 07:12:28]

Is this needed? I'm guessing the messages file brought this in transitively and
now you need it. Is that right?

[leonhsl(Using Gerrit), 2016/06/24 09:59:21]

Actually it's not my codes need it ;-)
https://codereview.chromium.org/2049783002 started to use base::WrapUnique but
did not include this header file explicitly, it implicitly uses via the message
file I delete here in this CL. To let all trybots happy I have to add this line
here. I did a rebase on ps#12, which will show the usage of base::WrapUnique
clearly.

Although, I've created a separate CL https://codereview.chromium.org/2095473003/
to add this explicitly. 

 #include "base/memory/scoped_vector.h"
 #include "base/native_library.h"
 #include "base/path_service.h"
@@ -32,7 +33,6 @@
 #include "chrome/common/secure_origin_whitelist.h"
 #include "chrome/common/url_constants.h"
 #include "chrome/grit/common_resources.h"
-#include "components/data_reduction_proxy/content/common/data_reduction_proxy_messages.h"
 #include "components/dom_distiller/core/url_constants.h"
 #include "components/version_info/version_info.h"
 #include "content/public/common/cdm_info.h"
@@ -602,11 +602,6 @@ void ChromeContentClient::AddAdditionalSchemes(
   savable_schemes->push_back(dom_distiller::kDomDistillerScheme);
 }
 
-bool ChromeContentClient::CanSendWhileSwappedOut(const IPC::Message* message) {

[Anand Mistry (off Chromium), 2016/06/24 07:12:28]

I honestly don't understand what's supposed to happen with swapped-out frames.
Someone that understand the effect of this should really take a look.

[leonhsl(Using Gerrit), 2016/06/24 09:59:21]

From my understanding, under swapped-out status RenderWidget::Send() can send
only some explicitly announced IPCs, here is just the annunciation for
DataReductionProxyViewHostMsg_IsDataReductionProxy. After switched to Mojo, the
restriction itself does not exist anymore, so I think we need to do nothing for
this.
Anyway, I'll try to find someone familiar with this to take a look.

[leonhsl(Using Gerrit), 2016/06/24 15:33:47]

Hi, tbansal@, megjablon@, I found that you have touched these codes before,
would you please help to take a look? Thanks.

[tbansal1, 2016/06/24 15:57:08]

leonhsi@, you are right. By default the IPCs are blocked for swapped out frames.
Here, we are trying to record page load metrics (e.g., page load time) if the
page used the data reduction proxy.

So, the renderer queries the browser if the page used the data reduction proxy.
This code punches a hole in the IPC mechanism to allow this message to go
through even after the swap out.

I am not familiar with Mojo, but if the IPC restriction (messages are blocked
after renderer is swapped out) is no longer there, then this code can be
removed.

-  return message->type() ==
-         DataReductionProxyViewHostMsg_IsDataReductionProxy::ID;
-}
-
 std::string ChromeContentClient::GetProduct() const {
   return ::GetProduct();
 }