Re: [rtcweb] realiable data service

Serge Lachapelle <sergel@google.com> Wed, 20 July 2011 19:11 UTC

Return-Path: <sergel@google.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 25DAE21F86DC for <rtcweb@ietfa.amsl.com>; Wed, 20 Jul 2011 12:11:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.676
X-Spam-Level:
X-Spam-Status: No, score=-105.676 tagged_above=-999 required=5 tests=[AWL=0.300, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, 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 lxwhR+DLN4rH for <rtcweb@ietfa.amsl.com>; Wed, 20 Jul 2011 12:11:49 -0700 (PDT)
Received: from smtp-out.google.com (smtp-out.google.com [216.239.44.51]) by ietfa.amsl.com (Postfix) with ESMTP id 4B58121F86D1 for <rtcweb@ietf.org>; Wed, 20 Jul 2011 12:11:49 -0700 (PDT)
Received: from wpaz13.hot.corp.google.com (wpaz13.hot.corp.google.com [172.24.198.77]) by smtp-out.google.com with ESMTP id p6KJBmHg014927 for <rtcweb@ietf.org>; Wed, 20 Jul 2011 12:11:48 -0700
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta; t=1311189108; bh=hSmMcVDZZ8nPnB09f9apriX7y9o=; h=MIME-Version:In-Reply-To:References:From:Date:Message-ID:Subject: To:Cc:Content-Type; b=XcCbQFuSl54TvBb+4NipXsthxO4cS3odwZdrd5uthpglsmeTORS82HWyPZjCOznAJ AeBpWVk1lmZacKr5LXfCA==
DomainKey-Signature: a=rsa-sha1; s=beta; d=google.com; c=nofws; q=dns; h=dkim-signature:mime-version:in-reply-to:references:from:date: message-id:subject:to:cc:content-type:x-system-of-record; b=xmCyHcYKrEq01CcjpvL7IM1jhF7Keyd4V9KAv2zs0i5JAwnnHlvqpnzpVdxaP443j VryW8R7NTxnO8MQDBmmSA==
Received: from yxl11 (yxl11.prod.google.com [10.190.3.203]) by wpaz13.hot.corp.google.com with ESMTP id p6KJB1v6010518 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NOT) for <rtcweb@ietf.org>; Wed, 20 Jul 2011 12:11:47 -0700
Received: by yxl11 with SMTP id 11so342696yxl.35 for <rtcweb@ietf.org>; Wed, 20 Jul 2011 12:11:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=beta; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=mJGYCAsL3dq916PPc4T9XsZax0YGaRkuyD4BlmhXJNc=; b=mLMUAGbTyqTeSl4xcuVLVKCIrPXiZ1LdZoJ6GbmthVJV6TGmDFFS20pvjI7vEuonyj rdDSmxS8Pi0YH3XMieFw==
Received: by 10.150.200.19 with SMTP id x19mr8250762ybf.264.1311189107240; Wed, 20 Jul 2011 12:11:47 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.150.201.18 with HTTP; Wed, 20 Jul 2011 12:11:17 -0700 (PDT)
In-Reply-To: <4E26F460.3080007@jesup.org>
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>
From: Serge Lachapelle <sergel@google.com>
Date: Wed, 20 Jul 2011 21:11:17 +0200
Message-ID: <CAMKM2Lw5+Y5t-Vecfp2KqJzP7Z8uZbQbw6b12PV5D=v-Hi3vPQ@mail.gmail.com>
To: Randell Jesup <randell1@jesup.org>
Content-Type: multipart/alternative; boundary="000e0cd348baf86d5504a885006f"
X-System-Of-Record: true
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 19:11:50 -0000

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