IETF Logo Mail Archive

Re: [rtcweb] Low Level Javascript API Proposal avail on the webrtc list

Iñaki Baz Castillo <ibc@aliax.net> Wed, 05 October 2011 09:28 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 831BC21F8B77 for <rtcweb@ietfa.amsl.com>; Wed, 5 Oct 2011 02:28:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.634
X-Spam-Level:
X-Spam-Status: No, score=-2.634 tagged_above=-999 required=5 tests=[AWL=0.043, 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 wdy8ldnuknsM for <rtcweb@ietfa.amsl.com>; Wed, 5 Oct 2011 02:28:29 -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 E42D821F8A35 for <rtcweb@ietf.org>; Wed, 5 Oct 2011 02:28:28 -0700 (PDT)
Received: by vcbfo11 with SMTP id fo11so1413267vcb.31 for <rtcweb@ietf.org>; Wed, 05 Oct 2011 02:31:36 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.52.89.177 with SMTP id bp17mr2079801vdb.447.1317807096258; Wed, 05 Oct 2011 02:31:36 -0700 (PDT)
Received: by 10.220.118.143 with HTTP; Wed, 5 Oct 2011 02:31:36 -0700 (PDT)
In-Reply-To: <4E8BC0ED.2020001@skype.net>
References: <545388B3-3189-4291-BD1D-52898B888F3E@phonefromhere.com> <CAD5OKxt_3bnODVCWxrrrKVWO3R3Or1FjhMOHwgUzq3-h6dW0LA@mail.gmail.com> <4E8BC0ED.2020001@skype.net>
Date: Wed, 05 Oct 2011 11:31:36 +0200
Message-ID: <CALiegfkU_qg5CN4g79jzRexw5W0ianWJGMPvPEt7KJSATu1CAg@mail.gmail.com>
From: Iñaki Baz Castillo <ibc@aliax.net>
To: Matthew Kaufman <matthew.kaufman@skype.net>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Cc: rtcweb@ietf.org
Subject: Re: [rtcweb] Low Level Javascript API Proposal avail on the webrtc list
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, 05 Oct 2011 09:28:29 -0000

2011/10/5 Matthew Kaufman <matthew.kaufman@skype.net>:
> This stuff is exactly what you'll need to add yet more code to solve if you
> try to bake SDP offer-answer into the browser to turn it 90% of the way into
> a SIP phone.
>
> And exactly what you *don't* need browser code to solve if it is done
> elsewhere (for instance, the server might be handling the entire SIP and SDP
> exchange and resolve forking issues at that end without involving the client
> at all.)

No please. The client CAN be intelligent, and that is how SIP usually
works (intelligence in endpoints rather than in servers).

You can do that if you want (you can build a custom
SIP<-->EasySimpleJsonProtocol gateway in server side), but please
don't mandate it. Let me to deal with SDP's in client side (at
JavaScript level), please. Others could choose what to do, but don't
force me to create a ugly application protocol gateway just because
some people prefer to make web clients as "simple as possible".

Regards.


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

v2.23.0 | Report a Bug | By Email