Re: [hybi] Framing take IV

Greg Wilkins <gregw@webtide.com> Wed, 04 August 2010 02:46 UTC

Return-Path: <gregw@webtide.com>
X-Original-To: hybi@core3.amsl.com
Delivered-To: hybi@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 74E823A6B89 for <hybi@core3.amsl.com>; Tue, 3 Aug 2010 19:46:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.711
X-Spam-Level:
X-Spam-Status: No, score=-1.711 tagged_above=-999 required=5 tests=[AWL=0.265, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001]
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 8yWLvIpeWfXo for <hybi@core3.amsl.com>; Tue, 3 Aug 2010 19:46:01 -0700 (PDT)
Received: from mail-fx0-f44.google.com (mail-fx0-f44.google.com [209.85.161.44]) by core3.amsl.com (Postfix) with ESMTP id 536AC3A68EA for <hybi@ietf.org>; Tue, 3 Aug 2010 19:46:01 -0700 (PDT)
Received: by fxm16 with SMTP id 16so1471777fxm.31 for <hybi@ietf.org>; Tue, 03 Aug 2010 19:46:29 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.223.113.5 with SMTP id y5mr8112473fap.93.1280889989693; Tue, 03 Aug 2010 19:46:29 -0700 (PDT)
Received: by 10.223.57.12 with HTTP; Tue, 3 Aug 2010 19:46:29 -0700 (PDT)
In-Reply-To: <20100804022719.GT27827@shareable.org>
References: <AANLkTinyrDoG5d_Ur6HVRy=SgMPjLzJtpJ++Ye=1DQdj@mail.gmail.com> <20100804022719.GT27827@shareable.org>
Date: Wed, 04 Aug 2010 12:46:29 +1000
Message-ID: <AANLkTi=MENta8H4A_ota=R==EJ3j0zAkPc7ai2qmsZiT@mail.gmail.com>
From: Greg Wilkins <gregw@webtide.com>
To: Jamie Lokier <jamie@shareable.org>
Content-Type: multipart/alternative; boundary="0016e6db7bc0d5005e048cf67015"
Cc: hybi@ietf.org
Subject: Re: [hybi] Framing take IV
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Server-Initiated HTTP <hybi.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Wed, 04 Aug 2010 02:46:02 -0000

Jamie,

Interesting idea.  I think we had assumed that negotiating extension opcodes
would be too complex, but what you have suggested looks like the start of a
simple solution.   Could you care to expand on it a bit more with exactly
how the client/server would agree on a final set of extended op-codes?

So it looks now like we have  4 possible extension approaches:

hixieasque - extension via defined opcodes
jamiesque - extension via negotiated opcodes
robertoesque - extension via per frame meta-data
martineque - extension via a dedicated mime frame


cheers



On 4 August 2010 12:27, Jamie Lokier <jamie@shareable.org> wrote:

>
> 4. Extension codes identified at handshake negotiation time, or a
> later negotiation time in control messages.
>
> For example: "WebSocket-Protocol: x-multiplex;control-byte=12,
> keepalive-aggregator;control-byte=13"
>
> Doing it at handshake time has the advantage that it's easily
> future-proof, very little needs to be defined up front, and simple
> implementations can ignore them entirely.
>
> -- Jamie
>