Re: [apps-discuss] IETF technical plenary: the end of application protocols

Cyrus Daboo <cyrus@daboo.name> Mon, 21 March 2011 16:50 UTC

Return-Path: <cyrus@daboo.name>
X-Original-To: apps-discuss@core3.amsl.com
Delivered-To: apps-discuss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AC56F28C0EC for <apps-discuss@core3.amsl.com>; Mon, 21 Mar 2011 09:50:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level:
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id T2yMl7Qi23we for <apps-discuss@core3.amsl.com>; Mon, 21 Mar 2011 09:50:31 -0700 (PDT)
Received: from daboo.name (daboo.name [151.201.22.177]) by core3.amsl.com (Postfix) with ESMTP id 3E18028C0EB for <apps-discuss@ietf.org>; Mon, 21 Mar 2011 09:50:31 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by daboo.name (Postfix) with ESMTP id 80B761C2D8438; Mon, 21 Mar 2011 12:52:03 -0400 (EDT)
X-Virus-Scanned: amavisd-new at daboo.name
Received: from daboo.name ([127.0.0.1]) by localhost (chewy.mulberrymail.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id H4KFOoiYUW3r; Mon, 21 Mar 2011 12:52:03 -0400 (EDT)
Received: from [17.101.34.182] (unknown [17.101.34.182]) by daboo.name (Postfix) with ESMTPSA id AAABB1C2D842B; Mon, 21 Mar 2011 12:52:01 -0400 (EDT)
Date: Mon, 21 Mar 2011 12:52:13 -0400
From: Cyrus Daboo <cyrus@daboo.name>
To: Scott Brim <scott.brim@gmail.com>, Peter Saint-Andre <stpeter@stpeter.im>
Message-ID: <DD76AA24190205BA0722B992@cyrus.local>
In-Reply-To: <AANLkTinWe6DPRF4sY1F1mhCed1cT52ZGvkQwDzjQNVoa@mail.gmail.com>
References: <4D87612E.3090900@dcrocker.net> <AANLkTik_f-4E8eoWbY2SowzTUdk53L3oiLZwFgoFS20y@mail.gmail.com> <4D876B4C.5070706@dcrocker.net> <4D877D30.9090502@stpeter.im> <AANLkTinWe6DPRF4sY1F1mhCed1cT52ZGvkQwDzjQNVoa@mail.gmail.com>
X-Mailer: Mulberry/4.1.0a1 (Mac OS X)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline; size="1127"
Cc: dcrocker@bbiw.net, Apps Discuss <apps-discuss@ietf.org>
Subject: Re: [apps-discuss] IETF technical plenary: the end of application protocols
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 21 Mar 2011 16:50:32 -0000

Hi Scott,

--On March 21, 2011 12:40:01 PM -0400 Scott Brim <scott.brim@gmail.com> 
wrote:

>> This is what I see, too: each service will have its own API / protocol,
>> resulting in wonderful vendor lock-in for the service provider but a
>> distinct lack of interoperability across services. We've just moved the
>> problem elsewhere.
>
> What interoperability do you need?  This isn't peer to peer, it's
> client/server.  All of the servers have de facto converged on the same
> client capabilities (http, html etc).  It's already standardized.

What if I have multiple service providers yet I want to present an 
aggregated view of all the data? e.g. the very common case of having 
multiple email accounts on different providers and wanting a "unified" 
inbox. With the "proprietary" approach of silo-ed web services, that 
becomes hard. Either I have to have a local app that understands each of 
the "proprietary" protocols and does the aggregation locally, or I have to 
rely on an intermediary to aggregate the data (which probably requires 
handing over credentials or doing some complicated crypto).

-- 
Cyrus Daboo