IETF Logo Mail Archive

Re: [rtcweb] On babies and bathwater (was Re: Summary of Application Developers' opinions of the current WebRTC API and SDP as a control surface)

Peter Thatcher <pthatcher@google.com> Fri, 19 July 2013 17:28 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 E295711E818F for <rtcweb@ietfa.amsl.com>; Fri, 19 Jul 2013 10:28:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.726
X-Spam-Level:
X-Spam-Status: No, score=-1.726 tagged_above=-999 required=5 tests=[AWL=0.251, 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 nds0xt+pFix3 for <rtcweb@ietfa.amsl.com>; Fri, 19 Jul 2013 10:28:21 -0700 (PDT)
Received: from mail-pb0-x229.google.com (mail-pb0-x229.google.com [IPv6:2607:f8b0:400e:c01::229]) by ietfa.amsl.com (Postfix) with ESMTP id 073A511E8194 for <rtcweb@ietf.org>; Fri, 19 Jul 2013 10:28:18 -0700 (PDT)
Received: by mail-pb0-f41.google.com with SMTP id rp16so4687891pbb.14 for <rtcweb@ietf.org>; Fri, 19 Jul 2013 10:27:56 -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=cpO8YJMHy80YhX/6i+9Ebw+9o2SxwrlnD30KSbsXMQU=; b=XtzK1Or6/SlFYZyrQO5iH8CtK1zDpvYKL5yx25cJw+Byut+Lml1MzuQZY+kVchvcxV Av87RBaI7yzxiBghSgyZSJIdl7y+rLzIUrsF0rLNG6PY1MVjAkFBYIdwTIYXmZXYuqLH 9lMpfR+bFyjxw1/TNPzyMGnRHDE+s5edB+o1NHUi+DNnhSvSPbNrKgGj05OUcfvgXajb i+TjSh3YFbEhLvJN3/l8FexAUo2V0/kECwTc6RYHKpfxt0eBDFPGYZba+LA5fJaBwbdj LeCvLLtZlNnPuh2QgP/j41WP2X7VM9G5CuTh+qnerPcLRNxdNl7KVDhT00+PxoQS7Se8 2cgw==
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=cpO8YJMHy80YhX/6i+9Ebw+9o2SxwrlnD30KSbsXMQU=; b=Lv41k6v5gWm5LR1osEgX+6JzrHe0iyJ8Q5Qw9EFJCGMcMpUzjKg1UvmJx9wgWe383g qwPOhkkfyVILTkiX2DuDS2hvM8uxUYPTP5TR+urQYIAeRMRuwyoHTbbp11OTHTj9MvcJ 0+Mtio8uNz361wb2xcfbZEZqxTkbbh93PvQ2Vo5mP+urXDkH85MoIPwM7tF5bvP8F4kx LPpv3Kx4QZNvIYAfLVriqn2D8btxbbhTbHBgcSahIiqugTYFZYwG3+xnJY89MS014vjL VU1+Ve92Rz89gwmjMQ62xrQ1+AencyBW+3mlkuIxhZNPHObQ7ddE9bcJEZNu4//uVZLd oy/g==
X-Received: by 10.66.14.196 with SMTP id r4mr19624909pac.57.1374254876384; Fri, 19 Jul 2013 10:27:56 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.66.78.195 with HTTP; Fri, 19 Jul 2013 10:27:16 -0700 (PDT)
In-Reply-To: <51E97677.1020902@nostrum.com>
References: <CAJrXDUGMohpBdi-ft-o_uE7ewFkw7wRY9x7gYEncjov7qi-Bew@mail.gmail.com> <CAJrXDUFxo8P8wxh8jX3019yPQOuwQ0eVdsFmRXsbWdWinnc5oA@mail.gmail.com> <CABcZeBOTKpmFC34waqZ4kA-P8t+E6yY9gX1JFCHhsBH0+CF-Qw@mail.gmail.com> <1447FA0C20ED5147A1AA0EF02890A64B1C30BC0F@ESESSMB209.ericsson.se> <CAD5OKxtKLMf_d=8GSMrqfNhDHPe9MFP2ZTKzZHFn9CyMr-gSVQ@mail.gmail.com> <1447FA0C20ED5147A1AA0EF02890A64B1C30C833@ESESSMB209.ericsson.se> <CAD5OKxvGfkgRp6tXwbOu_kVteHiBBqsyR5ixH18FMKjCNGO8VQ@mail.gmail.com> <1447FA0C20ED5147A1AA0EF02890A64B1C30CD1E@ESESSMB209.ericsson.se> <BLU401-EAS386F88B3FE140492B39B59693610@phx.gbl> <AE1A6B5FD507DC4FB3C5166F3A05A484213E41E7@TK5EX14MBXC265.redmond.corp.microsoft.com> <C50FDAD5-492C-4A83-AD6D-464242FB4A05@iii.ca> <CALiegfneUj=kzDjR_E1=S-bqAajaPUE3f_A2g8oGriFyPhamPA@mail.gmail.com> <51E96B5B.2050302@nostrum.com> <CABkgnnXa-eTzRHcLMnHam4c+1D9kkvRwi9=V-9P43+p+pKE_sw@mail.gmail.com> <CA+9kkMCjt2UHFynLqwns0J0f5ZtnxtMX3ppzR66e5q_rJ9D5Ug@mail.gmail.com> <51E97677.1020902@nostrum.com>
From: Peter Thatcher <pthatcher@google.com>
Date: Fri, 19 Jul 2013 10:27:16 -0700
Message-ID: <CAJrXDUGLwOEWCbZU8vS53pW9fZt_RdeKgmmw9My-dbgDn_PkqQ@mail.gmail.com>
To: Adam Roach <adam@nostrum.com>
Content-Type: multipart/alternative; boundary="bcaec51f99e5bd0b8404e1e0a559"
X-Gm-Message-State: ALoCoQmEPoNBxWfpmKkJbg4TN3hkYho0h62U36tLPmeeqPVOG6qapNEK4aO/tNTKXg7ANLq/WvdzumKmwTKfryZ3zCqZ6ODHnkrgJ41ggzUTE0AAWcPglyM+AowMR+xPpMslH9o+hR3ScHyFnftJU3f+JqFACNNYOHB+08Mov32kY89hGmj6XlO+tgUorc071fEVRlCt5+RK
Cc: "<rtcweb@ietf.org>" <rtcweb@ietf.org>, "public-webrtc@w3.org" <public-webrtc@w3.org>
Subject: Re: [rtcweb] On babies and bathwater (was Re: Summary of Application Developers' opinions of the current WebRTC API and SDP as a control surface)
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: Fri, 19 Jul 2013 17:28:22 -0000

On Fri, Jul 19, 2013 at 10:25 AM, Adam Roach <adam@nostrum.com> wrote:

>  On 7/19/13 12:07, Ted Hardie wrote:
>
> On Fri, Jul 19, 2013 at 9:54 AM, Martin Thomson <martin.thomson@gmail.com>wrote:
>
>>
>> Negotiation is a hole.  A vast, soul-sucking, waste of time.
>>
>>
> Even if you have the same javascript application downloaded, you will have
> disparate capabilities in the environments into which it is downloaded
> (browser/os/codecs/media sources/available network capacity).  Getting set
> intersection and preference order for those capabilities is something that
> applications actually want.  You may be able to move the pain of that
> around, but it isn't a waste of time.
>
>
> I can't +1 this hard enough. I certainly don't want every javascript
> application that makes use of the WebRTC API to independently discover that
> mobile terminal Foocom A1 runnning MobileOS 3.1.7(a) bogs down to unusable
> if you try to send it more than 320x200 video, and then try to solve that
> problem.
>
> Again and again, for every permutation of phone and operating system
> version.
>
> Yeah, someone has to do this kind of characterization, and some of it can
> be done real-time if you're interacting directly with the operating system.
> So... maybe we could add yet another API to WebRTC to allow applications to
> build this functionality themselves rather than counting on them
> characterizing the systems they care about and blowing up on the ones they
> don't.
>
> But, honestly, any course of action that relegates this to the
> applications seems to have the dual properties of forcing it to be
> implemented hundreds of thousands of times while making the actual user
> experience worse.
>

Hundreds of thousands of times?


>
>
> /a
>
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb
>
>

v2.27.6 | Report a Bug | By Email | System Status