- From: Max Solodovnikov via GitHub <sysbot+gh@w3.org>
- Date: Wed, 03 Jul 2019 18:28:36 +0000
- To: public-webrtc-logs@w3.org
@jan-ivar , great post , and finally a summary of annoying real world problems with current WebRTC media signalling APIs! A couple of extra thoughts about the proposed API:
- If intent is to simplify life for application developers, then I would suggest going step further and removing the need to provide the {rollback:true} altogether. SRD and current PC state should have all the information to decide whether it should trigger a rollback, or apply a remote answer (current signalling state + description type).
- It would be great if support for rolling back through SRD would remove the need to have the SLD rollback variant altogether. However, it does not seem to be possible to cover all scenarios with it. Namely, there is still a need to handle timeouts (offer/answer never reached remote endpoint) and errors (remote endpoint rejected offer for some reason), and SLD seems to be a better fit for this.
--
GitHub Notification of comment by solmaks
Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2166#issuecomment-508206783 using your GitHub account
Received on Wednesday, 3 July 2019 18:28:38 UTC