Re: [rtcweb] Let's define the purpose of WebRTC

Iñaki Baz Castillo <ibc@aliax.net> Tue, 15 November 2011 09:17 UTC

Return-Path: <ibc@aliax.net>
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 49ECF11E80C6 for <rtcweb@ietfa.amsl.com>; Tue, 15 Nov 2011 01:17:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.639
X-Spam-Level:
X-Spam-Status: No, score=-2.639 tagged_above=-999 required=5 tests=[AWL=0.038, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1]
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 saxZi8iDae53 for <rtcweb@ietfa.amsl.com>; Tue, 15 Nov 2011 01:17:17 -0800 (PST)
Received: from mail-vw0-f44.google.com (mail-vw0-f44.google.com [209.85.212.44]) by ietfa.amsl.com (Postfix) with ESMTP id B8BC411E80AA for <rtcweb@ietf.org>; Tue, 15 Nov 2011 01:17:17 -0800 (PST)
Received: by vws5 with SMTP id 5so7224412vws.31 for <rtcweb@ietf.org>; Tue, 15 Nov 2011 01:17:17 -0800 (PST)
Received: by 10.52.100.74 with SMTP id ew10mr41100513vdb.7.1321348637090; Tue, 15 Nov 2011 01:17:17 -0800 (PST)
MIME-Version: 1.0
Received: by 10.220.107.206 with HTTP; Tue, 15 Nov 2011 01:16:56 -0800 (PST)
In-Reply-To: <4EC1B5F1.1090604@skype.net>
References: <CALiegfkVNVAs_MyU_-4koA4zRwSn1-FwLjY9g_oZVkhi9rSK5Q@mail.gmail.com> <CAD5OKxt=k_Mon_GMs1w-bGMgpk12h6ZQ=FkoRVsTp4271iMSLA@mail.gmail.com> <CABcZeBNMTgwH-R_jd-AiEJ8tELTeFMNm-bAJohRg2RxD5e+kZQ@mail.gmail.com> <CAD6AjGRBmrAqB3CEWxtaXnryPA5App13S2jJPAt+7HwWZsQFzA@mail.gmail.com> <CABcZeBNtoizuRymVMxF4CdiLu1Nju63C0xkWJHjoarpxeLXjyA@mail.gmail.com> <CALiegfk=oJJ20GhKQBKA7aspHhUyQ-s+DR-qSi4XV455Nj718w@mail.gmail.com> <9C4C8AE2-4AFF-4553-9D19-556F12AC066E@phonefromhere.com> <9B907E0E-7FE7-4302-BDFA-CEEC12734B8C@edvina.net> <7BF02133-2A7E-48ED-982F-90B7868F9FB9@phonefromhere.com> <4EB74D06.8000006@jesup.org> <CAAJUQMihjTRgpO8hjgiYz5iLbWTncdXFO8nnRE9VDRND36-b2w@mail.gmail.com> <CALiegfmhst-2anmO1HMO1MVp=GFEjqOoG50wVKKMQic3AjxUsA@mail.gmail.com> <4EC1B5F1.1090604@skype.net>
From: Iñaki Baz Castillo <ibc@aliax.net>
Date: Tue, 15 Nov 2011 10:16:56 +0100
Message-ID: <CALiegfmajN4P+0qAB+2JtmayPao1SKLNq=ozJ-xdbxLQS1MTcw@mail.gmail.com>
To: Matthew Kaufman <matthew.kaufman@skype.net>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Cc: Randell Jesup <randell-ietf@jesup.org>, rtcweb@ietf.org
Subject: Re: [rtcweb] Let's define the purpose of WebRTC
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: Tue, 15 Nov 2011 09:17:18 -0000

2011/11/15 Matthew Kaufman <matthew.kaufman@skype.net>:
> Why *wouldn't* you want the JavaScript client code to participate in this
> decision?

It could, of course. Maybe a callback is executed for each forking
media session. If such callback returns "true" then the new session is
handled, otherwise it's ignored.

Another option would be set a "parameter" to allow media forking or
not prior to the call.

Or both options.

-- 
Iñaki Baz Castillo
<ibc@aliax.net>