Moved data reduction proxy initialization logic to ProfileImplIOData

android_webview/browser/aw_browser_context.cc

Index: android_webview/browser/aw_browser_context.cc
diff --git a/android_webview/browser/aw_browser_context.cc b/android_webview/browser/aw_browser_context.cc
index 4287b02514445696ed74f8dba84bf9ef92daf4de..484d18149abc0e5b3d7edfbc91bb5a66f3a5e571 100644
--- a/android_webview/browser/aw_browser_context.cc
+++ b/android_webview/browser/aw_browser_context.cc
@@ -104,7 +104,8 @@ void AwBrowserContext::PreMainMessageLoopRun() {
               data_reduction_proxy::DataReductionProxyParams::kAllowed)));
   data_reduction_proxy_auth_request_handler_.reset(

[willchan no longer on Chromium, 2014/07/29 00:26:56]

Is this code running on the UI thread? It looks like the
DataReductionProxyParams is created in ProfileImplIOData in the other way. Is
there a way to align these so we don't have the DataReductionProxyFoo objects
created on different threads depending on which application we're running in?

I assume there's an IO thread equivalent of AwBrowserContext that we could stash
this in.

[bengr, 2014/07/29 21:29:52]

I don't see one. Maybe Selim knows?

On 2014/07/29 00:26:56, willchan wrote:

       new DataReductionProxyAuthRequestHandler(
-          data_reduction_proxy_settings_->params()));
+          data_reduction_proxy_settings_->params(),
+          BrowserThread::GetMessageLoopProxyForThread(BrowserThread::IO)));
 #endif
 
   url_request_context_getter_ =