Skip to content
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

constructing RTCRtpReceiver without a transport #801

Closed
fippo opened this Issue Dec 29, 2017 · 0 comments

Comments

Projects
None yet
2 participants
@fippo
Copy link
Contributor

fippo commented Dec 29, 2017

Currently the RTCRtpReceiver constructor

[Constructor(DOMString kind, RTCDtlsTransport transport, 
    optional RTCDtlsTransport rtcpTransport),

requires a transport. With the 1.0 transceiver model one needs to construct receivers much earlier and it would be good to allow constructing the RTCRtpReceiver like this:

var receiver = new RTCRtpReceiver('audio');

and then call setTransport later.

Note that we also changed around the order of kind and transport compared to the initial Edge implementation which seems to suggest. Maybe there was the intention to make transport optional?

@fippo fippo referenced this issue Dec 29, 2017

Merged

wrap RTCRtpSender #41

aboba added a commit that referenced this issue Dec 31, 2017

@aboba aboba closed this Jan 15, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.