Re: [hybi] Web sockets and existing HTTP stacks

Jamie Lokier <jamie@shareable.org> Wed, 03 February 2010 01:49 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 C044F28C13D for <hybi@core3.amsl.com>; Tue, 2 Feb 2010 17:49:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.574
X-Spam-Level:
X-Spam-Status: No, score=-2.574 tagged_above=-999 required=5 tests=[AWL=0.025, 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 VL-ccyUP9RNa for <hybi@core3.amsl.com>; Tue, 2 Feb 2010 17:49:02 -0800 (PST)
Received: from mail2.shareable.org (mail2.shareable.org [80.68.89.115]) by core3.amsl.com (Postfix) with ESMTP id 07F653A682E for <hybi@ietf.org>; Tue, 2 Feb 2010 17:49:02 -0800 (PST)
Received: from jamie by mail2.shareable.org with local (Exim 4.63) (envelope-from <jamie@shareable.org>) id 1NcUNA-0004mQ-JJ; Wed, 03 Feb 2010 01:49:40 +0000
Date: Wed, 03 Feb 2010 01:49:40 +0000
From: Jamie Lokier <jamie@shareable.org>
To: SM <sm@resistor.net>
Message-ID: <20100203014940.GN32743@shareable.org>
References: <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> <20100201012914.GC20940@shareable.org> <6.2.5.6.2.20100131205550.06e1c700@resistor.net> <20100201105240.GD20940@shareable.org> <6.2.5.6.2.20100201054814.07f9bc18@resistor.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <6.2.5.6.2.20100201054814.07f9bc18@resistor.net>
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: Wed, 03 Feb 2010 01:49:02 -0000

SM wrote:
> If you are writing a protocol which requires a specific port, use a 
> different port.  If you can do HTTP Upgrade, run it on the HTTP port 

WebSocket does use HTTP Upgrade, so there's no problem.

-- Jami