Re: [hybi] Web sockets and existing HTTP stacks

Greg Wilkins <gregw@webtide.com> Tue, 02 February 2010 03:55 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 3CC2F3A6882 for <hybi@core3.amsl.com>; Mon, 1 Feb 2010 19:55:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.492
X-Spam-Level:
X-Spam-Status: No, score=-2.492 tagged_above=-999 required=5 tests=[AWL=0.107, 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 6GiORegj8OlQ for <hybi@core3.amsl.com>; Mon, 1 Feb 2010 19:55:19 -0800 (PST)
Received: from qw-out-2122.google.com (qw-out-2122.google.com [74.125.92.27]) by core3.amsl.com (Postfix) with ESMTP id 69DD63A684F for <hybi@ietf.org>; Mon, 1 Feb 2010 19:55:19 -0800 (PST)
Received: by qw-out-2122.google.com with SMTP id 9so1104537qwb.31 for <hybi@ietf.org>; Mon, 01 Feb 2010 19:55:51 -0800 (PST)
Received: by 10.224.15.130 with SMTP id k2mr2545928qaa.143.1265082950979; Mon, 01 Feb 2010 19:55:50 -0800 (PST)
Received: from ?10.10.1.11? (60-242-119-126.tpgi.com.au [60.242.119.126]) by mx.google.com with ESMTPS id 8sm11170493qwj.21.2010.02.01.19.55.47 (version=TLSv1/SSLv3 cipher=RC4-MD5); Mon, 01 Feb 2010 19:55:49 -0800 (PST)
Message-ID: <4B67A237.2040505@webtide.com>
Date: Tue, 02 Feb 2010 14:55:35 +1100
From: Greg Wilkins <gregw@webtide.com>
User-Agent: Thunderbird 2.0.0.23 (X11/20090817)
MIME-Version: 1.0
To: Ian Hickson <ian@hixie.ch>
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>
In-Reply-To: <Pine.LNX.4.64.1001310835410.3846@ps20323.dreamhostps.com>
X-Enigmail-Version: 0.95.7
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
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: Tue, 02 Feb 2010 03:55:20 -0000

Ian Hickson wrote:

> Similarly, the server, when parsing 
> the headers in "HTTP" mode, is unaffected by the order -- and indeed, the 
> Web Socket spec doesn't require _anything_ from the server in terms of 
> parsing the client request. You can completely ignore it for all the spec 
> cares. All that matters is that you send back a specific handshake. But if 
> you're sending back the handshake, then you're a Web Socket server, so why 
> do we need to follow HTTP rules? We've already established the client is a 
> Web Socket client, so what on earth is the point of using HTTP rules?

We need to follow HTTP rules because we are in a HTTP server
that has implemented the HTTP standard and until the CRLF
is sent after the 101 response, HTTP rules OK!


You think we are making up the difficulties we are having with this?