- From: Philipp Hancke via GitHub <sysbot+gh@w3.org>
- Date: Mon, 04 May 2020 20:54:09 +0000
- To: public-webrtc-logs@w3.org
> This feels like 'Undefined Behavior' conversations. You can tell developers Do not do that, but they are going to do it anyway. Why not design the API to be robust This is a philosophical discussion and one which has value. See [Postel was wrong](https://tools.ietf.org/html/draft-iab-protocol-maintenance-04) for one opinion. I'm on the "throw errors, dont assume the browser implementors are smarter" side. Doing a timing test for addIceCandidate that reliably covers all native code parts in *all* browsers is going to be somewhat impossible. Now where did I put the document with "p2p ice failure rates dropped *considerably* when postponing addIceCandidate slightly in chrome... (btw, you can still raise issues even without being a w3c member or invited expert... so far @dontcallmedom hasn't tried to stop me :-)) -- GitHub Notification of comment by fippo Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2519#issuecomment-623700034 using your GitHub account
Received on Monday, 4 May 2020 20:54:11 UTC