Moving WebRTC logging related files from content to chrome.

content/public/renderer/media/webrtc_log_message_delegate.h

+// Copyright (c) 2013 The Chromium Authors. All rights reserved.
+// Use of this source code is governed by a BSD-style license that can be
+// found in the LICENSE file.
+
+#ifndef CONTENT_PUBLIC_RENDERER_MEDIA_WEBRTC_LOG_MESSAGE_DELEGATE_H_
+#define CONTENT_PUBLIC_RENDERER_MEDIA_WEBRTC_LOG_MESSAGE_DELEGATE_H_
+
+#include <string>
+
+namespace content {
+
+// This interface is implemented by a handler in the embedder and used for
+// initializing the logging and passing log messages to the handler. The
+// purpose is to forward mainly libjingle log messages to Chrome (besides to the

[jam, 2013/05/29 16:25:48]

nit: don't mention chrome in content

[Henrik Grunell, 2013/05/29 16:56:59]

Changed to "embedder".

+// ordinary logging stream) that will be used for diagnostic purposes.
+class WebRtcLogMessageDelegate {
+ public:
+  virtual void InitLogging(const std::string& app_session_id,
+                           const std::string& app_url) = 0;

[jam, 2013/05/29 16:25:48]

what are these two parameters?

nit: also document these two methods

[Henrik Grunell, 2013/05/29 16:56:59]

The app session ID comes from the constraint value and is set by JS. The url is
the document url that triggered to start logging. (See
media_stream_dependency_factory.cc.)
 
Done.

+  virtual void LogMessage(const std::string& message) = 0;
+
+ protected:
+  virtual ~WebRtcLogMessageDelegate() {}
+};
+
+}  // namespace content
+
+#endif  // CONTENT_PUBLIC_RENDERER_MEDIA_WEBRTC_LOG_MESSAGE_DELEGATE_H_