javascript - Can I re-use an "offer" in WebRTC for mulitple connections? - Stack Overflow

admin管理员组

文章数量:1350369

I'm starting to learn WebRTC and have a working prototype using copy/paste here: (the prototype is meant to be run in two browser windows, unlike many other examples that run both sides in one window)

I understand that WebRTC is peer-to-peer and a I need a connection for every set of peers. However, I'm starting to think about signalling (no code yet) and I'm wondering about the "offer". In my prototype I see that clicking "create offer" multiple times results in the same string. So, if have client A, and connect to client B and C, it looks like I will send the same "offer" to both of them. If that's correct, it makes the first step of signalling easy - client A will always have the same offer, and I just have to gather responses from connected peers.

Is this a correct understanding?

I'm starting to learn WebRTC and have a working prototype using copy/paste here: https://github./aerik/webrtc (the prototype is meant to be run in two browser windows, unlike many other examples that run both sides in one window)

I understand that WebRTC is peer-to-peer and a I need a connection for every set of peers. However, I'm starting to think about signalling (no code yet) and I'm wondering about the "offer". In my prototype I see that clicking "create offer" multiple times results in the same string. So, if have client A, and connect to client B and C, it looks like I will send the same "offer" to both of them. If that's correct, it makes the first step of signalling easy - client A will always have the same offer, and I just have to gather responses from connected peers.

Is this a correct understanding?

• javascript
• webrtc

Share Improve this question Follow asked Dec 9, 2015 at 22:22 AerikAerik 2,31711 gold badge2929 silver badges4141 bronze badges

Add a ment  | 

1 Answer 1

Sorted by: Reset to default 11

It is not, a peer connection will generate different origin values for different offers (o= in the SDP).

Same peer connection offers will contain same <sess-id> but different <sess-version>.

Different peer connections will produce different <sess-id>

You can check it with the following snippet in Chrome:

var a = new RTCPeerConnection({});
a.createOffer().then(offer => $('#11').text(offer.sdp));
a.createOffer().then(offer => $('#12').text(offer.sdp));
var b = new RTCPeerConnection({});
b.createOffer().then(offer => $('#21').text(offer.sdp));
b.createOffer().then(offer => $('#22').text(offer.sdp));

<script src="https://ajax.googleapis./ajax/libs/jquery/2.1.1/jquery.min.js"></script>
First PC, first offer: <span id="11"></span><br/>
First PC, second offer: <span id="12"></span><br/>
Second PC, first offer: <span id="21"></span><br/>
Second PC, second offer: <span id="22"></span><br/>

You can find more info about the SDP in https://datatracker.ietf/doc/html/rfc4566#page-11

本文标签： javascriptCan I reuse an quotofferquot in WebRTC for mulitple connectionsStack Overflow