W3C home > Mailing lists > Public > public-webrtc@w3.org > May 2016

[webrtc-pc] How to manage RTCRtpTransceivers for incoming MediaStreamTracks?

From: Miguel París via GitHub <sysbot+gh@w3.org>
Date: Thu, 05 May 2016 13:58:44 +0000
To: public-webrtc@w3.org
Message-ID: <issues.opened-153238016-1462456723-sysbot+gh@w3.org>
mparis has just created a new issue for 
https://github.com/w3c/webrtc-pc:

== How to manage RTCRtpTransceivers for incoming MediaStreamTracks? ==
Hello,
when a remote MediaStreamTrack is processed, what happens if there is 
not any transceiver to manage it?

1. Should a new transceiver be created automatically?
2. Should the API have an event to notify the user if he wants to 
create a new transceiver to manage the incoming media? So:
  - if the user creates a new one the media will be accepted (local 
SDP with "a=recvonly" or "a=sendrecv")
  - if the user does not create a new one the media will be rejected 
(local SDP with: "a=sendonly" or "a=inactive")

>From my point of view, this question is quite interesting in the case 
that an endpoint does not know how many tracks the remote endpoint 
will offer it.

In the current document, [1] only says that a new receiver has to be 
created.

Refs
[1] 
http://w3c.github.io/webrtc-pc/#processing-remote-mediastreamtracks

Please view or discuss this issue at 
https://github.com/w3c/webrtc-pc/issues/623 using your GitHub account
Received on Thursday, 5 May 2016 13:58:46 UTC

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