- From: <bugzilla@jessica.w3.org>
- Date: Thu, 29 May 2014 19:12:19 +0000
- To: public-webrtc@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=25893 Justin Uberti <juberti@google.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |juberti@google.com --- Comment #4 from Justin Uberti <juberti@google.com> --- sendOnly/inactive will be controlled via RTCRtpSender/Receiver controls. OfferToReceiveAudio simply adds additional recvonly m-lines to work around the SDP limitation that the answerer can't respond with more than what was offered. There's no need for createOffer to have controls on exactly which direction should be signalled. Regarding #3, streams are never made to be sendonly through use of OfferToReceiveAudio, although an answer to a recvonly stream will necessarily be sendonly (or less). -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.
Received on Thursday, 29 May 2014 19:12:21 UTC