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

Re: sendonly streams in the offer

From: Martin Thomson <martin.thomson@gmail.com>
Date: Fri, 5 Apr 2013 15:18:28 -0700
Message-ID: <CABkgnnVxS_Yo2ZgAxRLL9Y=BfJyZgt7zw0_UJxj_4QBLMYpjxQ@mail.gmail.com>
To: Stefan HÃ¥kansson LK <stefan.lk.hakansson@ericsson.com>
Cc: "public-webrtc@w3.org" <public-webrtc@w3.org>
On 4 April 2013 22:10, Stefan HÃ¥kansson LK
<stefan.lk.hakansson@ericsson.com> wrote:
> I don't really see a need why the application would limit the number of
> inbound streams (e.g. by applying some setting on the PeerConnection).

I can think of a couple of reasons offhand.  An application might have
constraints on how it uses the available display area.  Alternatively,
an application that provides a relay might find this to be relevant.
(In combination with bandwidth constraints, of course).

> I can see a benefit of the receiving UA telling the sending UA how many
> streams it can handle, but that would depend on things like resolution,
> frame-rate, etc. and may not be that easy to express.

That's why this actually becomes more important.  It's an escape valve
for applications who can't deal with that complexity when they find
that the UA can't either.
Received on Friday, 5 April 2013 22:18:57 UTC

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