W3C home > Mailing lists > Public > public-webrtc@w3.org > June 2013

Re: Simultaneous Peer Connections

From: Dan Ristic <danr@pubnub.com>
Date: Mon, 24 Jun 2013 10:46:07 -0700
Message-ID: <CACVAH2d5MBnAtKWkZh1i2SHU6E_U-OnJsEzyTgmcjrN9H9_H6w@mail.gmail.com>
To: cowwoc <cowwoc@bbs.darktech.org>
Cc: public-webrtc <public-webrtc@w3.org>
Hm I have coded up a similar solution except all client side. Still a
rather annoying issue. Would be nice if you can accept a remote offer even
if your peer connection is in the offer state.

Dan


On Mon, Jun 24, 2013 at 10:39 AM, cowwoc <cowwoc@bbs.darktech.org> wrote:

> 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
>
>


-- 
Dan Ristic
Senior Front End Engineer
PubNub
Received on Monday, 24 June 2013 17:46:34 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 15:19:33 UTC