IETF Logo Mail Archive

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

Iñaki Baz Castillo <ibc@aliax.net> Mon, 07 November 2011 17:35 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 831FB21F8B66 for <rtcweb@ietfa.amsl.com>; Mon, 7 Nov 2011 09:35:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.636
X-Spam-Level:
X-Spam-Status: No, score=-2.636 tagged_above=-999 required=5 tests=[AWL=0.041, 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 zFBwwQuP3oWI for <rtcweb@ietfa.amsl.com>; Mon, 7 Nov 2011 09:35:13 -0800 (PST)
Received: from mail-vx0-f172.google.com (mail-vx0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id 8D51521F8B65 for <rtcweb@ietf.org>; Mon, 7 Nov 2011 09:35:13 -0800 (PST)
Received: by vcbfl11 with SMTP id fl11so4734730vcb.31 for <rtcweb@ietf.org>; Mon, 07 Nov 2011 09:35:13 -0800 (PST)
Received: by 10.52.33.239 with SMTP id u15mr14004699vdi.49.1320687313055; Mon, 07 Nov 2011 09:35:13 -0800 (PST)
MIME-Version: 1.0
Received: by 10.220.107.206 with HTTP; Mon, 7 Nov 2011 09:34:52 -0800 (PST)
In-Reply-To: <4EB806F7.2090603@alvestrand.no>
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> <4EB7FAED.4070104@jesup.org> <4EB806F7.2090603@alvestrand.no>
From: Iñaki Baz Castillo <ibc@aliax.net>
Date: Mon, 07 Nov 2011 18:34:52 +0100
Message-ID: <CALiegfn-DfOhd7mx7erCnscs+LaL755wGoiVtJSq6sutsKoAZQ@mail.gmail.com>
To: Harald Alvestrand <harald@alvestrand.no>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Cc: 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: Mon, 07 Nov 2011 17:35:14 -0000

2011/11/7 Harald Alvestrand <harald@alvestrand.no>:
> If we were doing a greenfield application, I'd let the server tell all the
> possible endpoints that they should set up a connection to the original
> caller, and forget about the caller calling anyone.
>
> The difference between caller and callee is a question of your level of
> abstraction.....

Of course that would be a possible scenario, but such scenario assumes
that the logic is in the webserver and clients are dumb. There is no
problem with that, of course. But I hope I must not assume that the JS
is dumb for all the possible WebRTC scenarios. I do need the concept
of "caller" and "callee".

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

v2.23.0 | Report a Bug | By Email