IETF Logo Mail Archive

Re: [hybi] WS framing alternative

Jamie Lokier <jamie@shareable.org> Fri, 30 October 2009 12:34 UTC

Return-Path: <jamie@shareable.org>
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 B53E33A6AA1 for <hybi@core3.amsl.com>; Fri, 30 Oct 2009 05:34:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.39
X-Spam-Level:
X-Spam-Status: No, score=-2.39 tagged_above=-999 required=5 tests=[AWL=0.209, BAYES_00=-2.599]
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 C7bXDli08uU9 for <hybi@core3.amsl.com>; Fri, 30 Oct 2009 05:34:16 -0700 (PDT)
Received: from mail2.shareable.org (mail2.shareable.org [80.68.89.115]) by core3.amsl.com (Postfix) with ESMTP id E59CE3A68D0 for <hybi@ietf.org>; Fri, 30 Oct 2009 05:34:15 -0700 (PDT)
Received: from jamie by mail2.shareable.org with local (Exim 4.63) (envelope-from <jamie@shareable.org>) id 1N3qgZ-00010P-KF; Fri, 30 Oct 2009 12:34:31 +0000
Date: Fri, 30 Oct 2009 12:34:31 +0000
From: Jamie Lokier <jamie@shareable.org>
To: Greg Wilkins <gregw@webtide.com>
Message-ID: <20091030123431.GB3579@shareable.org>
References: <8B0A9FCBB9832F43971E38010638454F0F1EA72C@SISPE7MB1.commscope.com> <Pine.LNX.4.62.0910270903080.9145@hixie.dreamhostps.com> <a9699fd20910270426u4aa508cepf557b362025ae5db@mail.gmail.com> <Pine.LNX.4.62.0910271824200.25616@hixie.dreamhostps.com> <4AE76137.8000603@webtide.com> <Pine.LNX.4.62.0910272118590.25608@hixie.dreamhostps.com> <20091029123121.GA24268@almeida.jinsky.com> <4AEA0E6C.1060607@webtide.com> <20091030025321.GD20292@shareable.org> <4AEA62B9.6040201@webtide.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <4AEA62B9.6040201@webtide.com>
User-Agent: Mutt/1.5.13 (2006-08-11)
Cc: hybi@ietf.org
Subject: Re: [hybi] WS framing alternative
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: Fri, 30 Oct 2009 12:34:16 -0000

Greg Wilkins wrote:
> Jamie Lokier wrote:
> > Let's not get confused about what will and won't work.
> > 
> > It doesn't matter whether WHATWG sanctions any new frame type or not:
> > you can't _use_ a frame type if the other end won't recognise it.
> > 
> > That's because the message boundaries are determined by recognising
> > the frame type byte, then parsing the message in a type-specific way.
> 
> 
> Is this true?
> 
> The high order byte is currently defined as selecting between
> sentinel or length encoding, and the 7 lower order bits are ignored.

No it's not true; you are right.  The frame length is determined
by the high order bit.

Sorry for reading too much into mailing list postings and not enough
reading the spec properly, which I will now do.

-- Jamie

v2.23.0 | Report a Bug | By Email