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

"Olle E. Johansson" <oej@edvina.net> Thu, 20 October 2011 14:56 UTC

Return-Path: <oej@edvina.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 9955A21F8BA8 for <rtcweb@ietfa.amsl.com>; Thu, 20 Oct 2011 07:56:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.816
X-Spam-Level:
X-Spam-Status: No, score=-1.816 tagged_above=-999 required=5 tests=[AWL=0.133, BAYES_00=-2.599, HELO_EQ_SE=0.35, 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 2HZ-myQFmRhP for <rtcweb@ietfa.amsl.com>; Thu, 20 Oct 2011 07:56:11 -0700 (PDT)
Received: from smtp7.webway.se (smtp7.webway.se [212.3.14.205]) by ietfa.amsl.com (Postfix) with ESMTP id 1A70021F8B94 for <rtcweb@ietf.org>; Thu, 20 Oct 2011 07:56:11 -0700 (PDT)
Received: from [192.168.20.63] (static-213-115-251-100.sme.bredbandsbolaget.se [213.115.251.100]) by smtp7.webway.se (Postfix) with ESMTPA id 76F22754BCD5; Thu, 20 Oct 2011 14:56:09 +0000 (UTC)
Mime-Version: 1.0 (Apple Message framework v1251.1)
Content-Type: text/plain; charset=iso-8859-1
From: "Olle E. Johansson" <oej@edvina.net>
In-Reply-To: <CALiegf=e05G3fwOZoKOYqtE7voPkanYEgWmGYJVSrFpiuJD-TQ@mail.gmail.com>
Date: Thu, 20 Oct 2011 16:56:11 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <9DC67F6E-B230-4026-9DE5-A4C11CC96575@edvina.net>
References: <9C8CA816-65FB-41A0-999C-4C43128CAAB4@danyork.org> <BLU152-W43CB8DACCEA54AA5558B2493EA0@phx.gbl> <E857C96A-0E73-486F-BF23-36BA897B449C@cisco.com> <BLU152-W19B31DA6C6DB2FE60FC51C93EB0@phx.gbl> <CALiegfkKhWwr4yY2vV-x2+01dys57_sYsSsoof=kEu5G3CL5oA@mail.gmail.com> <6DFC5313-2991-4FB5-811D-FC99D31F9298@edvina.net> <CALiegf=e05G3fwOZoKOYqtE7voPkanYEgWmGYJVSrFpiuJD-TQ@mail.gmail.com>
To: =?iso-8859-1?Q?I=F1aki_Baz_Castillo?= <ibc@aliax.net>
X-Mailer: Apple Mail (2.1251.1)
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: Thu, 20 Oct 2011 14:56:11 -0000

20 okt 2011 kl. 16:52 skrev Iñaki Baz Castillo:

> 2011/10/20 Olle E. Johansson <oej@edvina.net>;:
>> 20 okt 2011 kl. 16:39 skrev Iñaki Baz Castillo:
>> 
>>> 2011/10/20 Bernard Aboba <bernard_aboba@hotmail.com>;:
>>>> the APIs should also enable media to be sent over a websocket
>>> 
>>> WHAT??
>>> 
>> A more specific question: What are the use cases?
>> 
>> I understand that media over TCP is used in many apps today. While media over websocket over tcp over IP sounds just a bit too much, I am very curious on the use case.
> 
> 
> There is no use case. WebSocket is NOT designed for carrying media.

Right. But if we want to inject prompts in the call or save media files recorded, would that work? Not realtime.

Bernard - what did you have in mind when you wrote that?

/O