Hook up WebRTC logging extension API to the underlying functionality.

content/renderer/media/webrtc_logging_initializer.h

Index: content/renderer/media/webrtc_logging_initializer.h
diff --git a/content/renderer/media/webrtc_logging_initializer.h b/content/renderer/media/webrtc_logging_initializer.h
index 08abc66a7fddc7bd8bda0d44ccb99a35b977de61..b0fa072d8134c1464c9ac90fb0144c44e34f8225 100644
--- a/content/renderer/media/webrtc_logging_initializer.h
+++ b/content/renderer/media/webrtc_logging_initializer.h
@@ -11,10 +11,6 @@ namespace content {
 
 class WebRtcLogMessageDelegate;
 
-// Must be called on IO thread.
-void InitWebRtcLogging(const std::string& app_session_id,
-                       const std::string& app_url);
-
 // May be called on any thread.
 void WebRtcLogMessage(const std::string& message);

[no longer working on chromium, 2013/10/01 08:41:42]

It looks odd to have the initializer being used as a dispatcher to forward the
error message, why this file is needed? can you merge the method to other file,
like chrome_webrtc_log_message_delegate.cc?

[Henrik Grunell, 2013/10/02 12:47:18]

There was quite a long discussion about this with jam@, joi@ and tommi@. I can
give you details off-review if you like.

[no longer working on chromium, 2013/10/02 12:55:10]

All right, just keep what it is if that is some kind of conclusion from that
discussion.