While Chrome and Firefox each now include by default some limited support for WebRTC (and the related getUserMedia() capability), this demo represents the first time that a successful communication between the two browsers has been demonstrated, suggesting that longstanding promises by both of eventual interop are beginning to come to fruition. From conversations I had with experts from both companies at last week’s WebRTC/RTCWEB standards meeting in Boston, the plan is to remain interoperable from this point on, a lofty and crucial goal. Why crucial? Unlike the adoption-impacting interoperability challenges that SIP has faced due to significant numbers of independent hardware implementations, WebRTC promises faster overall interoperation because of the relatively smaller number of browsers that will have to support it.
It’s great that Mozilla and Google have now shown their willingness to make this happen. Microsoft and Apple, are you listening?
- W3C WebRTC Group Releases First Draft of API Specification For Browser-Based Communication
- WebRTC Working Group Begins Its Work Today With a Conf Call
- WebRTC Group Posts Minutes and Plans Face-to-Face Meeting This Coming Saturday in Quebec
- Want to Understand What RTCWEB/WebRTC Is All About? Read This Draft…
- Two New RTCWEB Mailing Lists For Separate IETF and W3C Activity