mallinath@webrtc.org 54fd70046d Remove ASSERT in TransportChannelProxy::SetImplementation, when ... proxy already set to same transport channel impl. Since session can call SetImplementation multiple times with or without BUNDLE, there are cases when SetImplementation is called with same impl (OnRemoteCandidates/PushdownTransportDescription/SetupMux). Also variables in cricket::TransportProxy like |connecting_| and |negotiated_| are accessed both between worker thread and signaling threads (which calls for bigger change on how session interacts with Transport and TransportChannelProxy). I have a created a separate bug to address later issue. Also if single thread used as worker and signaling thread, we can end up calling SetLocalDescription and OnRemoteCandidates in same call sequence, which will end up calling SetImplementation twice. R=wu@webrtc.org Review URL: https://webrtc-codereview.appspot.com/12019007 git-svn-id: http://webrtc.googlecode.com/svn/trunk@5944 4adac7df-926f-26a2-2b94-8c16560cd09d		2014-04-19 01:03:33 +00:00
..
base	Remove ASSERT in TransportChannelProxy::SetImplementation, when	2014-04-19 01:03:33 +00:00
client	(Auto)update libjingle 65152644-> 65219629	2014-04-19 00:00:31 +00:00