Data collection part of webrtc-internals implementation

This change implements the data collection part of webrtc-internals. 
RTCPeerConnectionHandler is an existing class living in the main renderer thread and knows about the status of a peer connection. With this CL, it reports every peer connection creation to PeerConnectionTracker.

PeerConnectionTracker is also running in the renderer process. It assigns an integer ID to each peer connectionstore and sends the basic peer connection info to PeerConnectionTrackerHost along with the ID.

PeerConnectionTrackerHost is running in the browser process in the IO thread. It simply passes anything it receives from PeerConnectionTracker to WebRTCInternals.

WebRTCInternals is a singlton running in the browser process. It sends the data received from PeerConnectionTrackerHost to every observer, i.e. webrtc-internals page. WebRTCInternalsUIObserver will be implemented in another change list.


BUG=168232


Review URL: https://chromiumcodereview.appspot.com/11753020

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@176012 0039d316-1c4b-4281-b951-d872f2087c98

1 files changed, 1 insertions, 0 deletions

diff --git a/ipc/ipc_message_start.h b/ipc/ipc_message_start.h
index baaebf6..339fcb2 100644
--- a/ipc/ipc_message_start.h
+++ b/ipc/ipc_message_start.h
@@ -72,6 +72,7 @@ enum IPCMessageStart {
   CCMsgStart,
   MediaPlayerMsgStart,
   TracingMsgStart,
+  PeerConnectionTrackerMsgStart,
   LastIPCMsgStart      // Must come last.
 };