Move the call to enable the WebRTC event log from PeerConnectionFactory to PeerConnection.

chrome/browser/media/webrtc_event_log_handler.h

Index: chrome/browser/media/webrtc_event_log_handler.h
diff --git a/chrome/browser/media/webrtc_event_log_handler.h b/chrome/browser/media/webrtc_event_log_handler.h
index 33eaa5cf1a1263304f4e88d9936932e22732be65..6bed72a0762f91e86db3805011ffc3893cb5287a 100644
--- a/chrome/browser/media/webrtc_event_log_handler.h
+++ b/chrome/browser/media/webrtc_event_log_handler.h
@@ -8,6 +8,7 @@
 #include <stddef.h>
 #include <stdint.h>
 
+#include <set>

[tommi (sloooow) - chröme, 2016/05/30 15:37:16]

do we still need this?

[Ivo-OOO until feb 6, 2016/05/31 08:18:30]

Good point, this is no longer needed.

 #include <string>
 
 #include "base/callback.h"
@@ -36,8 +37,9 @@ class WebRtcEventLogHandler
 
   explicit WebRtcEventLogHandler(Profile* profile);
 
-  // Starts an RTC event log. The call writes the most recent events to a
-  // file and then starts logging events for the given |delay|.
+  // Starts an RTC event log for each peerconnection on the specified |host|.
+  // The call writes the most recent events to a file and then starts logging
+  // events for the given |delay|.
   // If |delay| is zero, the logging will continue until
   // StopWebRtcEventLogging()
   // is explicitly invoked.
@@ -81,9 +83,6 @@ class WebRtcEventLogHandler
   // The profile associated with our renderer process.
   Profile* const profile_;
 
-  // Must be accessed on the UI thread.
-  bool is_rtc_event_logging_in_progress_;
-
   // This counter allows saving each log in a separate file.
   uint64_t current_rtc_event_log_id_;