WebRTC JavaScript Object API Rationale
Inaki Castillo, R. Shpount, Erik Lagerway, Robin Raymond
Abstract
Inaki Castillo, R. Shpount, Erik Lagerway, Robin Raymond
Abstract
This document describes the reasons why a JavaScript Object Model approach is a far better solution than using SDP [RFC4566] as a surface API for interfacing with WebRTC. The document outlines the issues and pitfalls as well as use cases that are difficult (or impossible) with SDP with offer / answer [RFC3264], and explains the benefits and goals of an alternative JavaScript object model approach.
A significance statement is not available in the OpenAlex record.
A contribution statement is not available in the OpenAlex record.
Method details are not available in the OpenAlex metadata.
Findings are not separately available in the OpenAlex metadata.
Limitations are not available in the OpenAlex metadata.
Application details are not available in the OpenAlex metadata.
This document describes the reasons why a JavaScript Object Model approach is a far better solution than using SDP [RFC4566] as a surface API for interfacing with WebRTC. The document outlines the issues and pitfalls as well as use cases that are difficult (or impossible) with SDP with offer / answer [RFC3264], and explains the benefits and goals of an alternative JavaScript object model approach.
Key concepts: JavaScript, WebRTC, Computer science, Object (grammar), Interfacing, HTML5, World Wide Web, Unobtrusive JavaScript