Added a callback function OnAddTrack to PeerConnectionObserver

webrtc/api/peerconnectioninterface.h

Index: webrtc/api/peerconnectioninterface.h
diff --git a/webrtc/api/peerconnectioninterface.h b/webrtc/api/peerconnectioninterface.h
index ea056bfc98fa2a39a1935a911988e3a1be35d897..dd587b8dccb6701920ebcbaa2c43e89111469ac0 100644
--- a/webrtc/api/peerconnectioninterface.h
+++ b/webrtc/api/peerconnectioninterface.h
@@ -593,6 +593,13 @@ class PeerConnectionObserver {
   // Called when the ICE connection receiving status changes.
   virtual void OnIceConnectionReceivingChange(bool receiving) {}
 
+  // Called when a track is added to streams.
+  // TODO(zhihuang) Make this a pure virtual method when all its subclasses
+  // implement it.
+  virtual void OnAddTrack(

[honghaiz3, 2016/11/17 01:19:02]

Should we also Add OnRemoveTrack?
If users expect to be notified when tracks are added, they may also expect to be
notified when tracks are removed. 

[Zhi Huang, 2016/11/17 01:42:06]

According to spec https://www.w3.org/TR/webrtc/#event-track, the event is fired
when "A new incoming MediaStreamTrack has been created, and an associated
RTCRtpReceiver has been added to the set of receivers.". 

I agree with you that it would make sense to have another callback. But I think
that can comes later in a separate CL, we can land this first so that this won't
be a blocker for both iOS and android.

+      rtc::scoped_refptr<RtpReceiverInterface> receiver,
+      std::vector<rtc::scoped_refptr<MediaStreamInterface>> streams) {}
+
  protected:
   // Dtor protected as objects shouldn't be deleted via this interface.
   ~PeerConnectionObserver() {}