Re: [hybi] Changing meaning of 1007 status code ("frame" => "message")

Iñaki Baz Castillo <ibc@aliax.net> Tue, 06 September 2011 16:35 UTC

Return-Path: <ibc@aliax.net>
X-Original-To: hybi@ietfa.amsl.com
Delivered-To: hybi@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CD12521F8BF3 for <hybi@ietfa.amsl.com>; Tue, 6 Sep 2011 09:35:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.646
X-Spam-Level:
X-Spam-Status: No, score=-2.646 tagged_above=-999 required=5 tests=[AWL=0.031, 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 28v8Rt+lrujt for <hybi@ietfa.amsl.com>; Tue, 6 Sep 2011 09:35:00 -0700 (PDT)
Received: from mail-qy0-f172.google.com (mail-qy0-f172.google.com [209.85.216.172]) by ietfa.amsl.com (Postfix) with ESMTP id 4D80421F8BF0 for <hybi@ietf.org>; Tue, 6 Sep 2011 09:35:00 -0700 (PDT)
Received: by qyk34 with SMTP id 34so697116qyk.10 for <hybi@ietf.org>; Tue, 06 Sep 2011 09:36:46 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.229.47.129 with SMTP id n1mr3986837qcf.215.1315327006728; Tue, 06 Sep 2011 09:36:46 -0700 (PDT)
Received: by 10.229.79.207 with HTTP; Tue, 6 Sep 2011 09:36:46 -0700 (PDT)
In-Reply-To: <634914A010D0B943A035D226786325D422C0EB8E0B@EXVMBX020-12.exch020.serverdata.net>
References: <CALiegf=D5K9H0uckc_zLVbaLieyu082g8kooAXa-3LkG+g_XGQ@mail.gmail.com> <634914A010D0B943A035D226786325D422C0EB8DB1@EXVMBX020-12.exch020.serverdata.net> <4E664964.2080601@gmail.com> <634914A010D0B943A035D226786325D422C0EB8E0B@EXVMBX020-12.exch020.serverdata.net>
Date: Tue, 06 Sep 2011 18:36:46 +0200
Message-ID: <CALiegfn-gD+vmQu97Z+tDb-SjBaygMOhQEUV4KGJ+8vtZbeGbw@mail.gmail.com>
From: Iñaki Baz Castillo <ibc@aliax.net>
To: Tobias Oberstein <tobias.oberstein@tavendo.de>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Cc: Hybi <hybi@ietf.org>
Subject: Re: [hybi] Changing meaning of 1007 status code ("frame" => "message")
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Server-Initiated HTTP <hybi.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/hybi>, <mailto:hybi-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/hybi>
List-Post: <mailto:hybi@ietf.org>
List-Help: <mailto:hybi-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/hybi>, <mailto:hybi-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Sep 2011 16:35:01 -0000

2011/9/6 Tobias Oberstein <tobias.oberstein@tavendo.de>:
>> I can understand the rationale for a streaming-based API (though I don't see
>> why already established multimedia protocols like SIP, RTSP or RTMP
>> wouldn't be a better choice here) but why would we both need message-
>
> None of these has the (promised) attraction of being "compatible with
> restricted network infrastructures".

Please, again the assumtion of an Internet based on HTTP and WebSocket
no. There si life out of port 80, really.

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