- From: ovelius via GitHub <sysbot+gh@w3.org>
- Date: Thu, 23 Jul 2020 15:41:10 +0000
- To: public-webrtc-logs@w3.org
> This can be shimed so I am not sure there is much value. > Also, the application might anyway need to handle the lack of these attributes for older browser version Just pointing out that older browsers/clients can be an argument against all changes =) But agree we have a workaround. I think, if we look at the bigger picture, that the real issue is this : For SFU applications in WebRTC you'll always end up with an SDP parser/creator in the application. IMHO in Unified Plan this actually took a small step backwards (at least for us) - as the removal of the PRANSWER concept requires more PeerConnection operations than before. This is in sharp contrast with the one to one scenario , there all the operations are clearly defined, and the SDP is completely opaque for the application. So I'd put on my wishlist for the future that WebRTC APIs could get first class support for SFU applications - instead of the "simulated peer to peer" approach we now seem to have. I hope this is somewhat of a fair conclusion, I would love to hear more about how this problem has been approached from other devs that have implemented an SFU application. Thanks! -- GitHub Notification of comment by ovelius Please view or discuss this issue at https://github.com/w3c/webrtc-extensions/issues/44#issuecomment-663079603 using your GitHub account
Received on Thursday, 23 July 2020 15:41:11 UTC