Passing NULL PeerConnectionIdentityService to Libjingle when Chrome is using openssl.

content/renderer/media/media_stream_dependency_factory.cc

Index: content/renderer/media/media_stream_dependency_factory.cc
diff --git a/content/renderer/media/media_stream_dependency_factory.cc b/content/renderer/media/media_stream_dependency_factory.cc
index 7f5e64aa187ffe65a2b1995e102f5a64b5809aef..8267a07fd1dc1776c2f7561fadea4a0171f2a0f5 100644
--- a/content/renderer/media/media_stream_dependency_factory.cc
+++ b/content/renderer/media/media_stream_dependency_factory.cc
@@ -550,9 +550,16 @@ MediaStreamDependencyFactory::CreatePeerConnection(
             socket_factory_.get(),
             web_frame);
 
+// The crypto APIs needed for generating identities are not implenented for
+// OPENSSL yet. So passing NULL to let Libjingle generate its own.
+// TODO(jiayl): remove the #if once the crypto APIs are implemented for OPENSSL.
   PeerConnectionIdentityService* identity_service =
+#if !defined(USE_OPENSSL)

[Ami GONE FROM CHROMIUM, 2013/08/09 17:14:35]

I don't really understand this.  Would it be useful to file a crbug (and point
to it from here) that enumerates the missing bits from openssl?

(should PCIS expose the fact that it is useless because of lack of underlying
impl details?  It seems strange to have to guard for this condition from here)

[jiayl, 2013/08/09 17:41:16]

Added the link to the existing bug.
I feel it's a cleaner interaction with Libjingle if NULL means "generate by
yourself" and non-NULL means "I can do it for you", instead of making Libjingle
checking error codes, which come from a header in Chrome.

       new PeerConnectionIdentityService(GURL(web_frame->document().url().spec())
                                             .GetOrigin());
+#else
+      NULL;
+#endif  // !defined(USE_OPENSSL)
 
   return pc_factory_->CreatePeerConnection(ice_servers,
                                            constraints,