Expose startNetLog / stopNetLog from HttpUrlRequestFactory.

components/cronet/android/java/src/org/chromium/net/ChromiumUrlRequestFactory.java

Index: components/cronet/android/java/src/org/chromium/net/ChromiumUrlRequestFactory.java
diff --git a/components/cronet/android/java/src/org/chromium/net/ChromiumUrlRequestFactory.java b/components/cronet/android/java/src/org/chromium/net/ChromiumUrlRequestFactory.java
index ff9fb7dc657e42f768312a3e2ddad2bdc92f81aa..13f4526226446c90b1d958bc1654868510655a61 100644
--- a/components/cronet/android/java/src/org/chromium/net/ChromiumUrlRequestFactory.java
+++ b/components/cronet/android/java/src/org/chromium/net/ChromiumUrlRequestFactory.java
@@ -55,6 +55,16 @@ public class ChromiumUrlRequestFactory extends HttpUrlRequestFactory {
                 headers, channel, listener);
     }
 
+    @Override
+    public void startNetLogToFile(String fileName) {

[Charles, 2014/09/26 18:23:13]

Do we need to worry about thread safety?

[mef, 2014/09/26 18:33:49]

You should not have to as long as context is not destroyed.

+        mRequestContext.startNetLogToFile(fileName);
+    }
+
+    @Override
+    public void stopNetLog() {
+        mRequestContext.stopNetLog();
+    }
+
     public ChromiumUrlRequestContext getRequestContext() {
         return mRequestContext;
     }