[PeerConnection] Implement asynchronous version of AddIceCandidate().
This is the same as the existing version, except it uses the Operations
Chain. As such, if an asynchronous operation that uses the chain is
currently pending, such as CreateOffer() or CreateAnswer(),
AddIceCandidate() will not happen until the previous operation
completes.
Bug: chromium:1019222
Change-Id: Ie6e5fc386fa9c29b5e2f8e3f65bfbaf9837d351c
Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/158741
Commit-Queue: Henrik Boström <hbos@webrtc.org>
Reviewed-by: Steve Anton <steveanton@webrtc.org>
Cr-Commit-Position: refs/heads/master@{#29704}
diff --git a/api/peer_connection_interface.h b/api/peer_connection_interface.h
index 7567ab1..52422c0 100644
--- a/api/peer_connection_interface.h
+++ b/api/peer_connection_interface.h
@@ -1039,7 +1039,14 @@
// A copy of the |candidate| will be created and added to the remote
// description. So the caller of this method still has the ownership of the
// |candidate|.
+ // TODO(hbos): The spec mandates chaining this operation onto the operations
+ // chain; deprecate and remove this version in favor of the callback-based
+ // signature.
virtual bool AddIceCandidate(const IceCandidateInterface* candidate) = 0;
+ // TODO(hbos): Remove default implementation once implemented by downstream
+ // projects.
+ virtual void AddIceCandidate(std::unique_ptr<IceCandidateInterface> candidate,
+ std::function<void(RTCError)> callback) {}
// Removes a group of remote candidates from the ICE agent. Needed mainly for
// continual gathering, to avoid an ever-growing list of candidates as