[ortc] constructing RTCRtpReceiver without a transport

fippo has just created a new issue for https://github.com/w3c/ortc:

== constructing RTCRtpReceiver without a transport ==
Currently the [RTCRtpReceiver constructor](http://draft.ortc.org/#rtcrtpreceiver*)
```
[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?

Please view or discuss this issue at https://github.com/w3c/ortc/issues/801 using your GitHub account

Received on Friday, 29 December 2017 19:03:41 UTC