Plumb media data from renderers up to MediaInternals in the browser process.

content/renderer/media/content_media_log.cc

+// Copyright (c) 2011 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.
+
+#include "content/renderer/media/content_media_log.h"
+
+#include "base/message_loop.h"
+#include "content/common/media/media_log_messages.h"
+#include "content/renderer/render_thread.h"
+
+ContentMediaLog::ContentMediaLog() : render_loop_(MessageLoop::current()) {
+  DCHECK(RenderThread::current()) <<
+      "ContentMediaLog must be constructed on the render thread";
+}
+
+void ContentMediaLog::AddEvent(Event* event) {
+  scoped_ptr<Event> e(event);
+
+  if (MessageLoop::current() == render_loop_) {

[jam, 2011/07/29 16:08:55]

you don't need to store the message loop pointer. You can check
RenderThread::current() to know if you're on the main thread or not

[Scott Franklin, 2011/07/29 22:30:25]

Right, but I then have no way of posting the task to the main thread. Unless
there is some other way to get a hold of its message loop?

If so, I can stop storing it, and the DCHECK above can go.

[jam, 2011/08/01 06:03:25]

of course, nm them :) although please use MessageLoopProxy instead of
MessageLoop, which is safer in case the MessageLoop object is destructing at
process shutdown. you can get it through
MessgeLoopProxy::CreateForCurrentThread()

[Scott Franklin, 2011/08/01 18:41:04]

Done.

+    RenderThread::current()->Send(new MediaLogMsg_MediaEvent(*e));
+  } else {
+    render_loop_->PostTask(FROM_HERE,
+        NewRunnableMethod(this, &ContentMediaLog::AddEvent, e.release()));
+  }
+}
+
+ContentMediaLog::~ContentMediaLog() {}