IETF Logo Mail Archive

Re: [rtcweb] Data transfer

Iñaki Baz Castillo <ibc@aliax.net> Fri, 16 September 2011 13:58 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 21B5721F8C0E for <rtcweb@ietfa.amsl.com>; Fri, 16 Sep 2011 06:58:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.648
X-Spam-Level:
X-Spam-Status: No, score=-2.648 tagged_above=-999 required=5 tests=[AWL=0.029, 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 5hVkzXEP+X5n for <rtcweb@ietfa.amsl.com>; Fri, 16 Sep 2011 06:58:56 -0700 (PDT)
Received: from mail-qw0-f45.google.com (mail-qw0-f45.google.com [209.85.216.45]) by ietfa.amsl.com (Postfix) with ESMTP id 6964721F8ABD for <rtcweb@ietf.org>; Fri, 16 Sep 2011 06:58:56 -0700 (PDT)
Received: by qwg2 with SMTP id 2so1385273qwg.4 for <rtcweb@ietf.org>; Fri, 16 Sep 2011 07:01:10 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.229.66.144 with SMTP id n16mr1569955qci.178.1316181670591; Fri, 16 Sep 2011 07:01:10 -0700 (PDT)
Received: by 10.229.79.207 with HTTP; Fri, 16 Sep 2011 07:01:10 -0700 (PDT)
In-Reply-To: <1C8B5EFA-2205-4B67-A800-4961FD6B116C@edvina.net>
References: <1C8B5EFA-2205-4B67-A800-4961FD6B116C@edvina.net>
Date: Fri, 16 Sep 2011 16:01:10 +0200
Message-ID: <CALiegfnOx9VeW6vmoHHV2Aopo1ECK7Ud51Lo0o0pAVBi=6LRjQ@mail.gmail.com>
From: =?UTF-8?Q?I=C3=B1aki_Baz_Castillo?= <ibc@aliax.net>
To: "Olle E. Johansson" <oej@edvina.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Cc: rtcweb@ietf.org
Subject: Re: [rtcweb] Data transfer
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: Fri, 16 Sep 2011 13:58:57 -0000

2011/9/16 Olle E. Johansson <oej@edvina.net>et>:
> "The goal is to enable innovation on
>
>   top of a set of basic components.  One core component is to enable
>   real-time media like audio and video, a second is to enable data
>   transfer directly between clients."
>
> Most of the discussions on the list has been about the media. What are the
> ideas for data transfer? Applications?

Hi. Just my opinion:

Having WebSocket protocol I don't see the need for a separate/specific
data transfer protocol within WebRTC. WebSocket already allows
bidirectional traffic for carrying long text or binary data (I means
even GigaBytes of data).

Also, HTML5 offers some cool features for "downloading" data received
by the JavaScript code. See a demo:

  http://html5-demos.appspot.com/static/a.download.html

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

v2.6.0 | Report a Bug | By Email