New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Handling of RTCRtpParameters #136
Comments
I have some questions about how this affects latching rules. Let us say that we want to specify the Payload Type for an incoming audio or video stream, but don't know the SSRC yet. Ideally, we would like to be able to receive the first stream without an RtpUnhandled event.
|
|
In another email, I pointed out that I think we should allow the On Tue, Jul 29, 2014 at 1:13 PM, aboba notifications@github.com wrote:
|
Suggestion from Peter: http://lists.w3.org/Archives/Public/public-ortc/2014Jul/0061.html |
And now I'm contradicting myself, because the more I think about it, the On Tue, Jul 29, 2014 at 2:29 PM, aboba notifications@github.com wrote:
|
Proposed Resolution: http://lists.w3.org/Archives/Public/public-ortc/2014Aug/0038.html |
w3c#93 Clarified onerror usage in sender and receiver objects, as noted in: w3c#95 Clarified SST-MS capability issue noted in: w3c#108 Clarification of send() and receive() usage as noted in: w3c#119 Changed ICE state diagram as noted in: w3c#122 Removed getParameters methods and changed send() method as noted in: w3c#136 Changed definition of framerateScale and resolutionScale as noted in: w3c#137 Substituted "muxId" for the "receiverId" as noted in: w3c#138 w3c#140 Clarified the setting of track.kind as described in: w3c#141 Added SSRC conflict event to the RTCRtpSender, as described in: w3c#143 Addressed the "end of candidates" issues noted in: w3c#142 w3c#144
At the July 20 ORTC CG meeting, it was proposed that the RTCRtpParameters object be completely filled in when passed to RTCRtpReceiver.receive() or RTCRtpSender.send(). If the passed RTCRtpParameters could not be implemented the browser would provide an Exception or Error rather than modifying RTCRtpParameters to indicate what it had implemented.
All of this put together implies that there is no longer a need for getParameters.
It also implies that we do not need a Promise for send.
The text was updated successfully, but these errors were encountered: