- From: cowwoc <cowwoc@bbs.darktech.org>
- Date: Mon, 24 Jun 2013 13:39:02 -0400
- To: public-webrtc@w3.org
On 24/06/2013 1:31 PM, Dan Ristic wrote:
> I am running into an issue with simultaneous peer connections between
> users. The issue is when pairing WebRTC with a presence service, if
> user A sees user B and initiates a connection at the same time that
> user B sees user A and initiates a connection back both of them are in
> offer states. Since they are both in offer states neither of them can
> accept the other offer request without either creating two connections
> or jumping through hoops to figure out who is the leader and who is
> the follower and dropping one of the requests.
>
> My question would be if the spec would be able to handle such a case
> and if not, what is the best way to get around this issue? I am pretty
> much building the jumping through hoops part into my JavaScript
> library to avoid this issue and it is proving to be a hassle of
> getting the timing right.
I ran into a similar problem. I ended up programming the server to
prevent this situation. Once a peer sends an offer, the server rejects
any offers from the second peer. If the first peer gets disconnected
their offer eventually times out and you can retry.
Gili
Received on Monday, 24 June 2013 17:39:44 UTC