Re: [rtcweb] New Draft - WebRTC JS Object API Model

Hadriel Kaplan <hadriel.kaplan@oracle.com> Wed, 03 July 2013 21:43 UTC

Return-Path: <hadriel.kaplan@oracle.com>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 28EC411E8267 for <rtcweb@ietfa.amsl.com>; Wed, 3 Jul 2013 14:43:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.499
X-Spam-Level:
X-Spam-Status: No, score=-6.499 tagged_above=-999 required=5 tests=[AWL=0.100, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QQXvG+4wYrey for <rtcweb@ietfa.amsl.com>; Wed, 3 Jul 2013 14:43:21 -0700 (PDT)
Received: from userp1040.oracle.com (userp1040.oracle.com [156.151.31.81]) by ietfa.amsl.com (Postfix) with ESMTP id B924011E8262 for <rtcweb@ietf.org>; Wed, 3 Jul 2013 14:43:21 -0700 (PDT)
Received: from ucsinet21.oracle.com (ucsinet21.oracle.com [156.151.31.93]) by userp1040.oracle.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.1) with ESMTP id r63LawmI025340 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 3 Jul 2013 21:36:59 GMT
Received: from userz7022.oracle.com (userz7022.oracle.com [156.151.31.86]) by ucsinet21.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id r63LhIYj012300 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 3 Jul 2013 21:43:19 GMT
Received: from abhmt110.oracle.com (abhmt110.oracle.com [141.146.116.62]) by userz7022.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id r63LhI6P019526; Wed, 3 Jul 2013 21:43:18 GMT
Received: from [10.1.21.23] (/10.5.21.23) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Wed, 03 Jul 2013 14:43:18 -0700
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: Hadriel Kaplan <hadriel.kaplan@oracle.com>
In-Reply-To: <51CA6FEE.6030702@hookflash.com>
Date: Wed, 3 Jul 2013 17:43:16 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <093EDF0B-AFEA-4979-AC72-23AF2FC5E8C7@oracle.com>
References: <51CA6FEE.6030702@hookflash.com>
To: Robin Raymond <robin@hookflash.com>
X-Mailer: Apple Mail (2.1508)
X-Source-IP: ucsinet21.oracle.com [156.151.31.93]
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] New Draft - WebRTC JS Object API Model
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Real-Time Communication in WEB-browsers working group list <rtcweb.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtcweb>
List-Post: <mailto:rtcweb@ietf.org>
List-Help: <mailto:rtcweb-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Jul 2013 21:43:27 -0000

You might also want to cite some of the reasons noted in this old draft:
http://tools.ietf.org/html/draft-kaplan-rtcweb-api-reqs-01

-hadriel


On Jun 26, 2013, at 12:37 AM, Robin Raymond <robin@hookflash.com> wrote:

> 
> According
>  to many, real adoption of WebRTC will not happen if we continue to 
> force everyone to use this SDP Offer/Answer methodology.  It is clearly 
> blocking our way forward and the amount of specification documentation 
> remaining needed for the browser vendors to produce a compatible SDP 
> based WebRTC engine in a browser is much more daunting than most are 
> willing to admit.
> 
> 
> The
>  draft rationale behind a JavaScript Object API model:
> 
> http://www.ietf.org/internet-drafts/draft-raymond-rtcweb-webrtc-js-obj-api-rationale-00.txt
> 
>  
> 
> Whereas:
> The
>  WebRTC JavaScript Object API & Shim document will be along shortly.
> 
> 
> We
>  wanted to get this initial rationale draft informational document out 
> right away. Everyone that has any interest should review the reasons and
>  concepts and comment before we get too far along on the details of an 
> actual API, the initial API will follow in the coming days.
> 
> 
> Best
>  regards,
> 
> Robin
>  Raymond
>  
> 
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb