API Requirements for WebRTC-enabled Browsers
draft-kaplan-rtcweb-api-reqs-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Hadriel Kaplan , Neil Stratford , Tim Panton | ||
| Last updated | 2012-05-03 (Latest revision 2011-10-31) | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
This document discusses the advantages and disadvantages of several proposed approaches to what type of API and architectural model WebRTC Browsers should expose and use. The document then defines the requirements for an API that treats the Browser as a library and interface as opposed to a self-contained application agent.
Authors
Hadriel Kaplan
Neil Stratford
Tim Panton
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)