- From: Martin Thomson via GitHub <sysbot+gh@w3.org>
- Date: Wed, 10 May 2017 22:14:40 +0000
- To: public-webrtc-logs@w3.org
If you change identity provider, the result from the first shouldn't be relevant at the point you call `createOffer` the second time. The UA can terminate or just ignore the results from the first; the second call will fetch the results from the second one, regardless of whether the first call is still outstanding or completed. After all, at the time of the second call to `createOffer`, the second identity provider has been set. In practice, I expect that the first `createOffer` call will either succeed or fail on its own merits. In Firefox, I think that it succeeds. We don't stop someone from creating multiple offers. (BTW, I think that in Firefox `createOffer` could be synchronous, aside from the identity provider calls, so my only real experience with asynchronous processing here is on the identity stuff.) -- GitHub Notification of comment by martinthomson Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1184#issuecomment-300628376 using your GitHub account
Received on Wednesday, 10 May 2017 22:14:47 UTC