Converts RTCOfferOptions to constriants in the glue code for createOffer.

content/browser/media/webrtc_internals.cc

Index: content/browser/media/webrtc_internals.cc
diff --git a/content/browser/media/webrtc_internals.cc b/content/browser/media/webrtc_internals.cc
index dcfc9051ab2a06c4f67ef11d03a4f1d28a316fe6..03afc1103d3ed282d457b190b7a7016a687acd86 100644
--- a/content/browser/media/webrtc_internals.cc
+++ b/content/browser/media/webrtc_internals.cc
@@ -67,7 +67,7 @@ void WebRTCInternals::OnAddPeerConnection(int render_process_id,
                                           ProcessId pid,
                                           int lid,
                                           const string& url,
-                                          const string& servers,
+                                          const string& rtc_configuration,

[vrk (LEFT CHROMIUM), 2014/07/23 01:13:05]

It looks like this also modifies updates webrtc-internals to use the new
PeerConnection constructor, with RTCConfiguration replacing the servers
parameter. Is this related to the createOffer/RTCOfferOptions change?

[jiayl, 2014/07/23 16:11:12]

It is, since this CL also add RTCTransportType, which will not be reported on
webrtc-internals if we don't change |servers| to |rtc_configuration|.

                                           const string& constraints) {
   DCHECK(BrowserThread::CurrentlyOn(BrowserThread::UI));
 
@@ -78,7 +78,7 @@ void WebRTCInternals::OnAddPeerConnection(int render_process_id,
   dict->SetInteger("rid", render_process_id);
   dict->SetInteger("pid", static_cast<int>(pid));
   dict->SetInteger("lid", lid);
-  dict->SetString("servers", servers);
+  dict->SetString("rtcConfiguration", rtc_configuration);
   dict->SetString("constraints", constraints);
   dict->SetString("url", url);
   peer_connection_data_.Append(dict);