Re: [webrtc-pc] editorial: media api introduction

Is it just the default direction of "sendrecv" you have a problem with? Or more generally, do you not like that it's possible to have a remote track pop up on the receive side before one is set on the send side?

Anyway, I agree the "corresponding tracks" sort of language is misleading, since tracks don't map 1:1 between the send/receive side. It would be good if this were explained somewhere, though it's not exactly straightforward so I don't know if the intro is the best place.

GitHub Notification of comment by taylor-b
Please view or discuss this issue at using your GitHub account

Received on Wednesday, 10 January 2018 18:14:55 UTC