Change the PeerConnection proxy templates to use blocking method calls instead of using Thread::Send. The problem with Thread::Send is that it processes incoming pending messages and for the proxies, this can mean that multiple incoming calls can concurrently run on the same thread, resulting in unexpected behavior.
Change the PeerConnection proxy templates to use blocking method calls instead of using Thread::Send.
The problem with Thread::Send is that it processes incoming pending messages and for the proxies,
this can mean that multiple incoming calls can concurrently run on the same thread, resulting in unexpected behavior.

See e.g. crbug.com/429740 (and more)

R=perkj@webrtc.org

Review URL: https://webrtc-codereview.appspot.com/28939004

Cr-Mirrored-From: https://chromium.googlesource.com/external/webrtc
Cr-Mirrored-Commit: 18de6f96226110206b015be961849381340d7d7c

sippet/talk,sippet/talk,sippet/talk,sippet/talk,sippet/talk