IETF Logo Mail Archive

Re: [hybi] Web sockets and existing HTTP stacks

Jamie Lokier <jamie@shareable.org> Mon, 01 February 2010 01:20 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 97AA63A69E3 for <hybi@core3.amsl.com>; Sun, 31 Jan 2010 17:20:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.366
X-Spam-Level:
X-Spam-Status: No, score=-2.366 tagged_above=-999 required=5 tests=[AWL=0.233, 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 HFZVNekUGIq9 for <hybi@core3.amsl.com>; Sun, 31 Jan 2010 17:20:39 -0800 (PST)
Received: from mail2.shareable.org (mail2.shareable.org [80.68.89.115]) by core3.amsl.com (Postfix) with ESMTP id 062D73A6889 for <hybi@ietf.org>; Sun, 31 Jan 2010 17:20:37 -0800 (PST)
Received: from jamie by mail2.shareable.org with local (Exim 4.63) (envelope-from <jamie@shareable.org>) id 1NbkyR-0002FM-NC; Mon, 01 Feb 2010 01:21:07 +0000
Date: Mon, 01 Feb 2010 01:21:07 +0000
From: Jamie Lokier <jamie@shareable.org>
To: L.Wood@surrey.ac.uk
Message-ID: <20100201012107.GB20940@shareable.org>
References: <557ae280911171402v7546e5e7n93a1e57f87dc10e5@mail.gmail.com> <557ae280911200711i5493e654k67c1f5f07336bfb9@mail.gmail.com> <Pine.LNX.4.62.0912032347360.15540@hixie.dreamhostps.com> <4B2C1D52.9020505@webtide.com> <5c902b9e0912181640n497169cdrfa71f9a2908e6ef3@mail.gmail.com> <20091219005442.GA10949@shareable.org> <4B2C287E.1030006@webtide.com> <Pine.LNX.4.64.1001310835410.3846@ps20323.dreamhostps.com> <5821ea241001311219j111d25a3h27fb2d05a2ece32d@mail.gmail.com> <A3BBB919-B5AF-4D7F-930F-63D40DB1B902@surrey.ac.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <A3BBB919-B5AF-4D7F-930F-63D40DB1B902@surrey.ac.uk>
User-Agent: Mutt/1.5.13 (2006-08-11)
Cc: hybi@ietf.org
Subject: Re: [hybi] Web sockets and existing HTTP stacks
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: Mon, 01 Feb 2010 01:20:41 -0000

L.Wood@surrey.ac.uk wrote:
> We already have BEEP for framing over TCP and to avoid
> head-of-line blocking. What would be wrong with that, apart
> from the fact that BEEP is already dead?

There are a few technical issues with BEEP, discussed several months
ago on the hybi list (consulte the archives).  It's usable but
over-complex in some respects and sub-optimal in others.  Nonetheless
there are some good things to learn from BEEP.

Is BEEP really dead? It had quite a long claimed list of users when I
looked last year.

Note that issues like multi-destination head-of-line blocking are not
addressed by WebSocket.  The current design expects individual
applications layered over WebSocket to deal with those issues using
their own application-specific protocol, where relevant.

-- Jamie

v2.23.0 | Report a Bug | By Email