IETF Logo Mail Archive

Re: [alto] WebSocket-based notifications

Peter Saint-Andre <stpeter@stpeter.im> Tue, 31 July 2012 18:26 UTC

Return-Path: <stpeter@stpeter.im>
X-Original-To: alto@ietfa.amsl.com
Delivered-To: alto@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6E68721F894B for <alto@ietfa.amsl.com>; Tue, 31 Jul 2012 11:26:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.568
X-Spam-Level:
X-Spam-Status: No, score=-102.568 tagged_above=-999 required=5 tests=[AWL=0.031, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 R7kGUgdATdil for <alto@ietfa.amsl.com>; Tue, 31 Jul 2012 11:26:42 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id 9AADD21F8940 for <alto@ietf.org>; Tue, 31 Jul 2012 11:26:42 -0700 (PDT)
Received: from [64.101.72.45] (unknown [64.101.72.45]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 383804009B; Tue, 31 Jul 2012 12:46:26 -0600 (MDT)
Message-ID: <50182360.40601@stpeter.im>
Date: Tue, 31 Jul 2012 12:26:40 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: "Diego R. Lopez" <diego@tid.es>
References: <5003C514.70806@telecomitalia.it> <7FA18E7BC523F04096632E46DA905D7A51DC0EA7@szxeml523-mbs.china.huawei.com> <500956C6.6050809@telecomitalia.it> <7FA18E7BC523F04096632E46DA905D7A51DC1F08@szxeml523-mbs.china.huawei.com> <500D00C9.6070706@telecomitalia.it> <7FA18E7BC523F04096632E46DA905D7A51DC1F55@szxeml523-mbs.china.huawei.com> <500E7B90.9030902@telecomitalia.it> <7FA18E7BC523F04096632E46DA905D7A51DC1F7C@szxeml523-mbs.china.huawei.com> <500FA3BC.5040003@telecomitalia.it> <7FA18E7BC523F04096632E46DA905D7A51DC1F9B@szxeml523-mbs.china.huawei.com> <CANUuoLp47j8ekOQ37T04eLUTH_pRfyRNBHhUFJhXTBER40RHkA@mail.gmail.com> <D209E532-B82C-4D5A-A92F-11936B6F58C9@tid.es>
In-Reply-To: <D209E532-B82C-4D5A-A92F-11936B6F58C9@tid.es>
X-Enigmail-Version: 1.4.3
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Cc: "alto@ietf.org" <alto@ietf.org>
Subject: Re: [alto] WebSocket-based notifications
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Application-Layer Traffic Optimization \(alto\) WG mailing list" <alto.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/alto>, <mailto:alto-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/alto>
List-Post: <mailto:alto@ietf.org>
List-Help: <mailto:alto-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/alto>, <mailto:alto-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 31 Jul 2012 18:26:43 -0000

On 7/29/12 5:43 PM, Diego R. Lopez wrote:
> Hi,
> 
> Just to add another bit of confusion...
> 
> When reading this thread I was wondering whether a solution based on
> bi-directional data streams, that would keep one single connection per
> client-server association while allowing for different resources to be
> queried and updated, could be considered.
> 
> What I have in mind is the use of XMPP for bi-directional ALTO
> interactions. Apart from the features outlined in the paragraph above, it
> does fit well with ALTO encoding and operational semantics, and
> there is a well established corpus of (many of them open) implementations.

It certainly seems to me that we could use XMPP here. However, I'll need
to read draft-marocco-alto-ws before providing more detailed comments. :)

Peter

-- 
Peter Saint-Andre
https://stpeter.im/

v2.23.0 | Report a Bug | By Email