IETF Logo Mail Archive

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

Saúl Ibarra Corretgé <saul@ag-projects.com> Wed, 19 October 2011 17:57 UTC

Return-Path: <saul@ag-projects.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 A49B921F8C53 for <rtcweb@ietfa.amsl.com>; Wed, 19 Oct 2011 10:57:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.688
X-Spam-Level:
X-Spam-Status: No, score=-1.688 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_MISMATCH_NET=0.611, MIME_8BIT_HEADER=0.3]
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 gHWVXuGIKHz8 for <rtcweb@ietfa.amsl.com>; Wed, 19 Oct 2011 10:57:29 -0700 (PDT)
Received: from mail.sipthor.net (node06.dns-hosting.info [85.17.186.6]) by ietfa.amsl.com (Postfix) with ESMTP id 3164321F8C5C for <rtcweb@ietf.org>; Wed, 19 Oct 2011 10:57:29 -0700 (PDT)
Received: by mail.sipthor.net (Postfix, from userid 5001) id 8FC6CB01A5; Wed, 19 Oct 2011 19:57:28 +0200 (CEST)
Received: from [192.168.99.36] (ip3e830637.speed.planet.nl [62.131.6.55]) by mail.sipthor.net (Postfix) with ESMTPSA id D8E58B019E; Wed, 19 Oct 2011 19:57:25 +0200 (CEST)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset="iso-8859-1"
From: Saúl Ibarra Corretgé <saul@ag-projects.com>
In-Reply-To: <CALiegfm9CH1W94j6cY-vSFPF39HntBKB_zdfTpewpSMAf_UgPQ@mail.gmail.com>
Date: Wed, 19 Oct 2011 19:57:24 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <7DBDE7E0-E6D9-4F3A-8343-4E465E9B817A@ag-projects.com>
References: <9C8CA816-65FB-41A0-999C-4C43128CAAB4@danyork.org> <C4D9E706-A420-4BA0-9C0D-D9676578527D@ag-projects.com> <CALiegfm9CH1W94j6cY-vSFPF39HntBKB_zdfTpewpSMAf_UgPQ@mail.gmail.com>
To: Iñaki Baz Castillo <ibc@aliax.net>
X-Mailer: Apple Mail (2.1084)
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:57:29 -0000

On Oct 19, 2011, at 7:50 PM, Iñaki Baz Castillo wrote:

> 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).
> 

That was not my point. My point was that Phono connects to a predefined server, it doesn't really matter if it's open or close, what matters is the fact that a server is provided for the cool stuff to happen.

--
Saúl Ibarra Corretgé
AG Projects

v2.23.0 | Report a Bug | By Email