IETF Logo Mail Archive

Re: [rtcweb] A plea for simplicity, marketability - and... who are we designing RTCWEB for?

Iñaki Baz Castillo <ibc@aliax.net> Wed, 19 October 2011 17:50 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 BC92121F8B62 for <rtcweb@ietfa.amsl.com>; Wed, 19 Oct 2011 10:50:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.638
X-Spam-Level:
X-Spam-Status: No, score=-2.638 tagged_above=-999 required=5 tests=[AWL=0.039, 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 q6M7JVMaNGAZ for <rtcweb@ietfa.amsl.com>; Wed, 19 Oct 2011 10:50:48 -0700 (PDT)
Received: from mail-vx0-f172.google.com (mail-vx0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id 322AE21F8B65 for <rtcweb@ietf.org>; Wed, 19 Oct 2011 10:50:48 -0700 (PDT)
Received: by vcbfo1 with SMTP id fo1so2151328vcb.31 for <rtcweb@ietf.org>; Wed, 19 Oct 2011 10:50:47 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.52.35.34 with SMTP id e2mr7629181vdj.52.1319046647547; Wed, 19 Oct 2011 10:50:47 -0700 (PDT)
Received: by 10.220.118.143 with HTTP; Wed, 19 Oct 2011 10:50:47 -0700 (PDT)
In-Reply-To: <C4D9E706-A420-4BA0-9C0D-D9676578527D@ag-projects.com>
References: <9C8CA816-65FB-41A0-999C-4C43128CAAB4@danyork.org> <C4D9E706-A420-4BA0-9C0D-D9676578527D@ag-projects.com>
Date: Wed, 19 Oct 2011 19:50:47 +0200
Message-ID: <CALiegfm9CH1W94j6cY-vSFPF39HntBKB_zdfTpewpSMAf_UgPQ@mail.gmail.com>
From: Iñaki Baz Castillo <ibc@aliax.net>
To: Saúl Ibarra Corretgé <saul@ag-projects.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Cc: rtcweb@ietf.org
Subject: Re: [rtcweb] A plea for simplicity, marketability - and... who are we designing RTCWEB for?
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, 19 Oct 2011 17:50:48 -0000

2011/10/19 Saúl Ibarra Corretgé <saul@ag-projects.com>:
> Well, lets take Phono as an example. Why can people build cool things with it? Because it's a simple library and developers don't need to do much, right? That's only true because someone (Voxeo in the case of Phono) provides a server for it. Inaki and Jose could very well build a jQuery plugin on top of that jsSIP library which would connect you through *their* OverSIP servers and it would work just as good. A phone in your browser, 10 lines of JS.

This is an important note. When a web developer uses Phone it's just
using the JS provided by Phono, but it must connect to Phono servers
(that is a product, a service, NOT an open technology).

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

v2.23.0 | Report a Bug | By Email