W3C home > Mailing lists > Public > public-webrtc@w3.org > July 2011

Moz/Cisco API proposal: multiple connections

From: Stefan Håkansson LK <stefan.lk.hakansson@ericsson.com>
Date: Wed, 13 Jul 2011 15:43:12 +0200
To: "public-webrtc@w3.org" <public-webrtc@w3.org>
Message-ID: <BBF498F2D030E84AB1179E24D1AC41D616C389F0A4@ESESSCMS0362.eemea.ericsson.se>
In the proposal there is a discussion on multiple connections per PeerConnection object: "Using a single PeerConnection to handle multiple incoming connections presents some unique challenges, but also has the desirable property of being able to stream out a single set of MediaStreams to multiple peers (which can also be changed mid-session). "

To me the most natural way would be to have one PeerConnection object per peer. Then, if the same set of streams are sent to each peer, of course there should be only one encoding, framing, packetization etc. But this is an optimization that can be handled in the implementation, and need not to be visible at the JS API level.

Received on Wednesday, 13 July 2011 13:43:36 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:17:20 UTC