Re: [rtcweb] realiable data service
Bernard Aboba <bernard_aboba@hotmail.com> Wed, 20 July 2011 20:37 UTC
Return-Path: <bernard_aboba@hotmail.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 E639A21F8511 for <rtcweb@ietfa.amsl.com>; Wed, 20 Jul 2011 13:37:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.246
X-Spam-Level:
X-Spam-Status: No, score=-102.246 tagged_above=-999 required=5 tests=[AWL=-0.248, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_46=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id m7koYPsDG7x8 for <rtcweb@ietfa.amsl.com>; Wed, 20 Jul 2011 13:37:40 -0700 (PDT)
Received: from blu0-omc4-s3.blu0.hotmail.com (blu0-omc4-s3.blu0.hotmail.com [65.55.111.142]) by ietfa.amsl.com (Postfix) with ESMTP id 3817421F8500 for <rtcweb@ietf.org>; Wed, 20 Jul 2011 13:37:40 -0700 (PDT)
Received: from BLU152-W15 ([65.55.111.137]) by blu0-omc4-s3.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675); Wed, 20 Jul 2011 13:37:39 -0700
Message-ID: <BLU152-W1590548F13B148AEA77C95934C0@phx.gbl>
Content-Type: multipart/alternative; boundary="_6c07b856-6875-4b21-a8e4-840099774aef_"
X-Originating-IP: [98.203.198.61]
From: Bernard Aboba <bernard_aboba@hotmail.com>
To: sergel@google.com
Date: Wed, 20 Jul 2011 13:37:39 -0700
Importance: Normal
In-Reply-To: <CAMKM2Lxs-xSSG0muOg_ukGJtSKxE5gLG94EfhGuoAiZJfDUFmA@mail.gmail.com>
References: <CAMKM2LzpVcS9jjXjfffuXy+YQmjZXbdaSJBp+O22nLd4N2KAvg@mail.gmail.com>, <CA4AFBFA.1C4B5%henry.sinnreich@gmail.com>, <CAOJ7v-3R0PeUSdVZ0n7AE08J=UjYMJqJ+4-Vkbj7w0qs0u=Rgw@mail.gmail.com>, <4E25B2BA.8000004@jesup.org> <4E25B893.6010200@jitsi.org>, <CAMKM2Lz_sgrmHVpuuGfyukmxdO-+qaWjyOhQzU6vTSDaAwytxQ@mail.gmail.com>, <4E26A354.2020306@ericsson.com> <4E26F460.3080007@jesup.org>, <CAMKM2Lw5+Y5t-Vecfp2KqJzP7Z8uZbQbw6b12PV5D=v-Hi3vPQ@mail.gmail.com>, <CAMKM2Lxs-xSSG0muOg_ukGJtSKxE5gLG94EfhGuoAiZJfDUFmA@mail.gmail.com>
MIME-Version: 1.0
X-OriginalArrivalTime: 20 Jul 2011 20:37:39.0711 (UTC) FILETIME=[DE0F68F0:01CC471C]
Cc: rtcweb@ietf.org
Subject: Re: [rtcweb] realiable data service
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, 20 Jul 2011 20:37:41 -0000
Agreed. To make this a bit more concrete. From your perspective, what is the preferred mechanism for file transfer in XMPP, and what would it take to support this in a browser? From: sergel@google.com Date: Wed, 20 Jul 2011 22:00:32 +0200 To: randell1@jesup.org CC: rtcweb@ietf.org Subject: Re: [rtcweb] realiable data service Just to put the file transfer debate to bed from my end, I am not against reliable channels, in fact, a ton of innovation can come from it when made available to browsers. I just want to avoid any re-engineering of what browsers offer today as much as possible. /Serge On Wed, Jul 20, 2011 at 21:11, Serge Lachapelle <sergel@google.com> wrote: For other cases (file xfer), yes you can use those - but the problem is that when you want to transfer to the person you're chatting with, you would need to use another service, agree on it, deal with the semantics/accounts/limits/etc for that service, etc. A horrible user experience. Even if it was "hidden" by the application, it would be problematic and subject to breakage continually. If I am building a 1:1 or hangout style application connecting my users, I would simply integrate it or add the functionality in the web UI I am building. This is very easy to do with web services these days. /Serge -- Serge Lachapelle | Product Manager | sergel@google.com | +46 732 01 22 32 Google Sweden AB | Kungsbron 2, SE-111 22 Stockholm | Org. nr. 556656-6880 Apparently, this footer is required in Europe. Apologies. This email may be confidential or privileged. If you received this communication by mistake, please don't forward it to anyone else,please erase all copies and attachments, and please let me know that it went to the wrong person. Thanks. _______________________________________________ rtcweb mailing list rtcweb@ietf.org https://www.ietf.org/mailman/listinfo/rtcweb
- Re: [rtcweb] Non-media data service consensus and… Jonathan Rosenberg
- [rtcweb] Non-media data service consensus and req… Magnus Westerlund
- Re: [rtcweb] Non-media data service consensus and… Emil Ivov
- Re: [rtcweb] Non-media data service consensus and… Bernard Aboba
- Re: [rtcweb] Non-media data service consensus and… Emil Ivov
- Re: [rtcweb] Non-media data service consensus and… Matthew Kaufman
- Re: [rtcweb] Non-media data service consensus and… Christopher Blizzard
- Re: [rtcweb] Non-media data service consensus and… Bernard Aboba
- Re: [rtcweb] Non-media data service consensus and… Matthew Kaufman
- Re: [rtcweb] Non-media data service consensus and… Emil Ivov
- Re: [rtcweb] Non-media data service consensus and… Igor Faynberg
- Re: [rtcweb] Non-media data service consensus and… Emil Ivov
- Re: [rtcweb] Non-media data service consensus and… Magnus Westerlund
- Re: [rtcweb] Non-media data service consensus and… Manuel Simoni
- Re: [rtcweb] Non-media data service consensus and… Magnus Westerlund
- Re: [rtcweb] Non-media data service consensus and… Igor Faynberg
- Re: [rtcweb] Non-media data service consensus and… Timothy B. Terriberry
- Re: [rtcweb] Non-media data service consensus and… Dzonatas Sol
- Re: [rtcweb] Non-media data service consensus and… Dzonatas Sol
- Re: [rtcweb] Non-media data service consensus and… Randell Jesup
- Re: [rtcweb] Non-media data service consensus and… Magnus Westerlund
- Re: [rtcweb] Non-media data service consensus and… Manuel Simoni
- Re: [rtcweb] Non-media data service consensus and… Dzonatas Sol
- Re: [rtcweb] Non-media data service consensus and… Christopher Blizzard
- Re: [rtcweb] Non-media data service consensus and… Cullen Jennings
- Re: [rtcweb] Non-media data service consensus and… Cullen Jennings
- Re: [rtcweb] Non-media data service consensus and… Randell Jesup
- [rtcweb] Consensus Call on Non-media data service… Magnus Westerlund
- Re: [rtcweb] Consensus Call on Non-media data ser… Dzonatas Sol
- Re: [rtcweb] Consensus Call on Non-media data ser… Dzonatas Sol
- Re: [rtcweb] Consensus Call on Non-media data ser… Dzonatas Sol
- Re: [rtcweb] Consensus Call on Non-media data ser… Magnus Westerlund
- Re: [rtcweb] Consensus Call on Non-media data ser… Dzonatas Sol
- [rtcweb] realiable data service Cullen Jennings
- Re: [rtcweb] realiable data service Tim Panton
- Re: [rtcweb] realiable data service Emil Ivov
- Re: [rtcweb] realiable data service Dzonatas Sol
- Re: [rtcweb] realiable data service Dzonatas Sol
- Re: [rtcweb] realiable data service Randell Jesup
- Re: [rtcweb] realiable data service Dzonatas Sol
- Re: [rtcweb] realiable data service Dzonatas Sol
- Re: [rtcweb] realiable data service Ted Hardie
- Re: [rtcweb] realiable data service Serge Lachapelle
- Re: [rtcweb] realiable data service Silvia Pfeiffer
- Re: [rtcweb] realiable data service Tim Panton
- Re: [rtcweb] realiable data service Magnus Westerlund
- Re: [rtcweb] realiable data service Tim Panton
- Re: [rtcweb] realiable data service Randell Jesup
- Re: [rtcweb] realiable data service Ted Hardie
- Re: [rtcweb] realiable data service Cullen Jennings
- Re: [rtcweb] realiable data service Cullen Jennings
- Re: [rtcweb] realiable data service Tim Panton
- Re: [rtcweb] realiable data service Cullen Jennings
- Re: [rtcweb] realiable data service Dzonatas Sol
- Re: [rtcweb] realiable data service Matthew Kaufman
- Re: [rtcweb] realiable data service Cullen Jennings
- Re: [rtcweb] realiable data service Randell Jesup
- Re: [rtcweb] realiable data service Magnus Westerlund
- Re: [rtcweb] realiable data service Henry Sinnreich
- Re: [rtcweb] realiable data service Justin Uberti
- Re: [rtcweb] realiable data service Randell Jesup
- Re: [rtcweb] realiable data service Emil Ivov
- Re: [rtcweb] realiable data service Serge Lachapelle
- Re: [rtcweb] realiable data service Emil Ivov
- Re: [rtcweb] realiable data service Dzonatas Sol
- Re: [rtcweb] realiable data service Dzonatas Sol
- Re: [rtcweb] realiable data service Dzonatas Sol
- Re: [rtcweb] realiable data service Cullen Jennings
- Re: [rtcweb] realiable data service Cullen Jennings
- Re: [rtcweb] realiable data service Stefan Håkansson LK
- Re: [rtcweb] realiable data service Emil Ivov
- [rtcweb] PseudoTCP implementation (Re: realiable … Harald Alvestrand
- Re: [rtcweb] realiable data service Randell Jesup
- Re: [rtcweb] PseudoTCP implementation (Re: realia… Justin Uberti
- Re: [rtcweb] realiable data service Serge Lachapelle
- Re: [rtcweb] realiable data service Serge Lachapelle
- Re: [rtcweb] realiable data service Bernard Aboba
- Re: [rtcweb] realiable data service Peter Saint-Andre
- Re: [rtcweb] PseudoTCP implementation (Re: realia… Cullen Jennings
- Re: [rtcweb] PseudoTCP implementation (Re: realia… Tim Panton
- Re: [rtcweb] PseudoTCP implementation (Re: realia… Emil Ivov
- Re: [rtcweb] PseudoTCP implementation (Re: realia… Justin Uberti
- Re: [rtcweb] PseudoTCP implementation (Re: realia… Cullen Jennings
- Re: [rtcweb] PseudoTCP implementation (Re: realia… Justin Uberti
- Re: [rtcweb] PseudoTCP implementation (Re: realia… Harald Alvestrand
- Re: [rtcweb] PseudoTCP implementation (Re: realia… Justin Uberti