- From: henbos via GitHub <sysbot+gh@w3.org>
- Date: Thu, 25 Apr 2019 09:50:53 +0000
- To: public-webrtc-logs@w3.org
Note: It might be reasonable to allow setCodecPreference to work such that a transceiver only works for sending or only works for receiving if you are interested in @jan-ivar's one-way transceiver model, but you if you include a sendrecv-capable codec in your list and then only ever negotiate sendonly or recvonly then you'll end up only negotiating the one-way capable codec. So I don't think it's worth this API for that edge-case. -- GitHub Notification of comment by henbos Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2183#issuecomment-486605662 using your GitHub account
Received on Thursday, 25 April 2019 09:50:54 UTC