Generates the DTLS identity in browser process and returns it to render process.

content/renderer/media/dtls_identity_service.cc

+// 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.
+
+#include "content/renderer/media/dtls_identity_service.h"
+
+#include "content/common/media/dtls_identity_messages.h"
+#include "content/renderer/render_thread_impl.h"
+
+namespace content {
+
+DTLSIdentityService::DTLSIdentityService(
+    const GURL& origin,
+    DTLSIdentityObserver* observer)
+    : origin_(origin) {
+  DCHECK(observer);
+  observer_.reset(observer);
+}
+
+DTLSIdentityService::~DTLSIdentityService() {}
+
+void DTLSIdentityService::GetOrGenerateIdentity(
+    const std::string& identity_name,
+    const std::string& common_name) {
+  RenderThreadImpl::current()->Send(
+      new DTLSIdentityMsg_GetOrGenerate(origin_, identity_name, common_name));
+}
+
+bool DTLSIdentityService::OnControlMessageReceived(
+    const IPC::Message& message) {
+  bool handled = true;
+  IPC_BEGIN_MESSAGE_MAP(DTLSIdentityService, message)
+    IPC_MESSAGE_HANDLER(DTLSIdentityHostMsg_IdentityReady, OnIdentityReady)
+    IPC_MESSAGE_UNHANDLED(handled = false)
+  IPC_END_MESSAGE_MAP()
+  return handled;
+}
+
+void DTLSIdentityService::OnIdentityReady(const std::string& certificate,

[Ami GONE FROM CHROMIUM, 2013/06/06 18:28:51]

Is it ok that libjingle will ask for the identity on the render thread but get
the answer callback on the I/O thread, or do you need to trampoline this
callback back to the requesting thread here?

[jiayl, 2013/06/06 21:00:08]

The callback is always called on the render thread as well.

+                                          const std::string& private_key) {
+  observer_->OnCompleted(certificate, private_key);
+}
+
+}  // namespace content