Hi Everyone,
In preparation for a presentation I was doing talking about How to Build
Your First WebRTC Application, I ended up going to through the full
process of building three different end to end WebRTC Web Applications.
As a result, I have some reflection comments, questions, etc below on
the experience I had while building these applications with the current
state of our implementation:
* Chrome required establishing ICE between two remote peers, while
Firefox did not. Why is this the case? Do we ever fire anything but
a null candidate back from onicecandidate in Firefox?
* Chrome has already decided to unprefix RTCIceCandidate and
RTCSessionDescription. Why hasn't Firefox done so?
* In the process of building an interoperable WebRTC application
between Chrome and Firefox, when I did not provide
DtlsStrpKeyAgreement to true as an optional constraint to Chrome,
Firefox would fail to establish the handshake by reporting an error
of "DCB has not been created" during the addIceCandidate function.
Why is this the case?
* addIceCandidate in the W3C spec only supports one argument, but
Firefox's implementation supports more than one argument. Why are we
doing something different here?
--
Sincerely,
Jason Smith
Desktop QA Engineer
Mozilla Corporation
https://quality.mozilla.com
_______________________________________________
dev-media mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-media
