IETF Logo Mail Archive

Re: [rtcweb] Proposal for a JS API for NoPlan (adding multiple sources without encoding them in SDP)

Peter Thatcher <pthatcher@google.com> Thu, 27 June 2013 05:26 UTC

Return-Path: <pthatcher@google.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 6139A21F9C00 for <rtcweb@ietfa.amsl.com>; Wed, 26 Jun 2013 22:26:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.912
X-Spam-Level:
X-Spam-Status: No, score=-1.912 tagged_above=-999 required=5 tests=[AWL=0.065, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
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 BQEvUb8XLHQt for <rtcweb@ietfa.amsl.com>; Wed, 26 Jun 2013 22:26:10 -0700 (PDT)
Received: from mail-pd0-x234.google.com (mail-pd0-x234.google.com [IPv6:2607:f8b0:400e:c02::234]) by ietfa.amsl.com (Postfix) with ESMTP id A092A21F9BFF for <rtcweb@ietf.org>; Wed, 26 Jun 2013 22:26:10 -0700 (PDT)
Received: by mail-pd0-f180.google.com with SMTP id 10so171486pdi.11 for <rtcweb@ietf.org>; Wed, 26 Jun 2013 22:26:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=XJ7RtCaau7e9lp4iEfIZYWTbzzp8zrZdnLJgZIVAYpE=; b=DkAXc8BC8gWzLlxq5faw5tK8jCE57IG4vut9e3NIRkTvcWlerjWvZhgOGthWUSEPT4 OuhRZHDuE/h95ZlbTLVYLOFSnrltlR8+5Lo9GudFLRLVPp9GtP9BkBQ9n/gwpFN70cL4 nbJ3EvumVlIPKDlp4r81bmcw1+fNZ9ayP7w/9Te4fNymYEEXqRHx33ODSRd3vNc9FOso egqaYKaLP6NS4gw4Q0xEQuRC4+3Q+NOrv01uFv1w79W31nEp+qoAom2fleoEFkO203lo zGAN9/Gs6EMQCUmSt76Z/c/PZDyqnBfBnIOGCYirYnal1tqvfGtMDJdMJdGjWwDBe6Dh XRdA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:x-gm-message-state; bh=XJ7RtCaau7e9lp4iEfIZYWTbzzp8zrZdnLJgZIVAYpE=; b=F8a3p363o0ZTH544+Gf+6XIrSRMDM8njKjUXKwFBEzgwKNH85tQTDf2Kye74wt91qy h5zlWV+QYkYDBkZItjJ/rO8hGzYwTqA3od3tc7OAR8dPFb4e+iSjQwyAguCkWwbz/1fL 51Ihb9bJBJYt9QdS+hYXOGAODkTq8HWT2t09aSlbCh9SCp4XqrXA5uupOn0ihNjtexgj 13Cy/ODi34MJmTcHaJlapBBFbjHzSBwuvqvmT53Gbtqh428/omjLkENZmDxmAGS0R2/c GFmjRUFyDk3yGyEhVdQ0ZT/cpS/U31keQj2zd5YiP5BqnwW7JthzMoquoB+eU4YJsmjs Jn9w==
X-Received: by 10.68.13.42 with SMTP id e10mr4181729pbc.23.1372310767612; Wed, 26 Jun 2013 22:26:07 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.66.216.163 with HTTP; Wed, 26 Jun 2013 22:25:27 -0700 (PDT)
In-Reply-To: <51CBCAC8.7070107@hookflash.com>
References: <CAJrXDUHdoxLTsofiwLBdwBNnCCkCBgjSdbmLaXrNEPODMrsSVA@mail.gmail.com> <CABkgnnUmRpanfpwryyiCUsOdMLzrd74n-4LXaj_AK3aLe0yQ8Q@mail.gmail.com> <51BF5F00.90705@jitsi.org> <CABkgnnWTvJYG1_HQWz3pZw633rgadeKzx472MTzzFMuq073RgQ@mail.gmail.com> <CALiegfkZcXrNR3CXY--d4ObZMV2z7NEpgdyVHtVtROVtDQsT6A@mail.gmail.com> <CAD5OKxs95gAmYoCr-EB6LaDFW7vaFfpF7=9fu_aCfV=LjwsVpg@mail.gmail.com> <BLU169-W13367E5FDE396829D364D62938C0@phx.gbl> <CAJrXDUEO-prozZPYAm2snfgUXhS5nKRN-ZXWdU1VGfXGnOTAfg@mail.gmail.com> <BLU403-EAS148552B821ED225C03D441D93750@phx.gbl> <CAJrXDUEbD7PuKkwF-oDOZJ-7gWr=GR0sft39t_0_5vDHs9YWOQ@mail.gmail.com> <51CBCAC8.7070107@hookflash.com>
From: Peter Thatcher <pthatcher@google.com>
Date: Wed, 26 Jun 2013 22:25:27 -0700
Message-ID: <CAJrXDUFgPGGZvHXsdswn8ErqWQYDN7P_ruTroUHULP10hHjipw@mail.gmail.com>
To: Robin Raymond <robin@hookflash.com>
Content-Type: multipart/related; boundary=bcaec51f9083d3634504e01bffde
X-Gm-Message-State: ALoCoQlgPBG/6ivQdFUOZH31GY287d5n39BJiM9+ngRdZ2mMyE35TcpN6gd6d6uN1NEqDxz3ZFnryGmK3Qzuq042rdYC5oS+GoUO10Si3wibl1A/4WYVKtqcY8Fgv9Jzy28GlCtFABO7BReyRAvNUqAPViiCL+TmUd/35Zfc9zKjWfmHrzYwCmrBVyQm55bWn4XB1yBskyl0
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] Proposal for a JS API for NoPlan (adding multiple sources without encoding them in SDP)
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: Thu, 27 Jun 2013 05:26:11 -0000

That's a good point about porting code from browser to node.js.  I hadn't
thought of that.

More great feedback from the JS developers!


On Wed, Jun 26, 2013 at 10:16 PM, Robin Raymond <robin@hookflash.com> wrote:

>
> True, node.js doesn't have to use the same code in their implementation
> and they are free to deviate from the WebRTC path. But it would be highly
> desirable if they could use the same API as it would ensure a greater level
> of compatibility between client and servers where common JS libraries can
> be used. Plus node JS can be used to produce not just server apps but HTML5
> based applications, so having a compatible library for those kind of
> applications is valuable too.
>
> -Robin
>
>   Peter Thatcher <pthatcher@google.com>
>  27 June, 2013 1:01 AM
> If Node.js wants a cleaner API, it's can certainly create one.  It's not
> at all constrained by what goes in the browser or what the WGs decide.  In
> fact, that would be an interesting way to explore a cleaner API to see how
> well it works.
>
>
>
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb
>   Bernard Aboba <bernard_aboba@hotmail.com>
>  26 June, 2013 8:19 PM
> I do think No Plan represents progress toward containing the SDP monster
> in WebRTC 1.0, particularly for video scenarios. However, I also agree with
> Robin's arguments against SDP and O/ A, particularly for a server-side API
> (e.g. Node.js modules) where the current API makes no sense at all. So my
> perspective is to contain the monster in 1.0, then go with 2.0 first on
> server, then on the browser.
>
> On Jun 17, 2013, at 10:34 PM, "Peter Thatcher" <pthatcher@google.com>
> wrote:
>
>

v2.1.5 | Report a Bug | By Email