Re: [hybi] #1: HTTP Compliance

Willy Tarreau <w@1wt.eu> Thu, 22 July 2010 07:01 UTC

Return-Path: <w@1wt.eu>
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 F29783A67D7 for <hybi@core3.amsl.com>; Thu, 22 Jul 2010 00:01:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.096
X-Spam-Level:
X-Spam-Status: No, score=-3.096 tagged_above=-999 required=5 tests=[AWL=-1.053, BAYES_00=-2.599, HELO_IS_SMALL6=0.556]
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 ttxtJBw1Wt8H for <hybi@core3.amsl.com>; Thu, 22 Jul 2010 00:01:36 -0700 (PDT)
Received: from 1wt.eu (1wt.eu [62.212.114.60]) by core3.amsl.com (Postfix) with ESMTP id BA1AD3A6834 for <hybi@ietf.org>; Thu, 22 Jul 2010 00:01:35 -0700 (PDT)
Received: (from willy@localhost) by mail.home.local (8.14.4/8.14.4/Submit) id o6M71k5c010044; Thu, 22 Jul 2010 09:01:46 +0200
Date: Thu, 22 Jul 2010 09:01:46 +0200
From: Willy Tarreau <w@1wt.eu>
To: John Tamplin <jat@google.com>
Message-ID: <20100722070146.GA10032@1wt.eu>
References: <068.d07026741c6694cd80652d2a7d34f236@tools.ietf.org> <4BF106AD.6020506@webtide.com> <A42E692A-7210-4FF1-AB4F-CFB3E8C38756@apple.com> <AANLkTinorjXFsTH=TvhhF-+e3Eyen8EA2qL7wFCmqpYe@mail.gmail.com> <Pine.LNX.4.64.1007212247590.7242@ps20323.dreamhostps.com> <20100721230350.GF6475@1wt.eu> <Pine.LNX.4.64.1007220500080.7242@ps20323.dreamhostps.com> <AANLkTi=xe5fPpL2KHygYaLtsDdi5G44R5-thhwAJOSoW@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <AANLkTi=xe5fPpL2KHygYaLtsDdi5G44R5-thhwAJOSoW@mail.gmail.com>
User-Agent: Mutt/1.4.2.3i
Cc: "hybi@ietf.org" <hybi@ietf.org>
Subject: Re: [hybi] #1: HTTP Compliance
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: Thu, 22 Jul 2010 07:01:37 -0000

On Thu, Jul 22, 2010 at 02:50:34AM -0400, John Tamplin wrote:
> On Thu, Jul 22, 2010 at 2:32 AM, Ian Hickson <ian@hixie.ch> wrote:
> > I see no advantage in the common case to using the same software for both.
> > It's far easier to just host them separately.
> >
> > Why don't people use the same software for HTTP and DNS? Or IMAP and SMTP?
> > Or IRC and FTP? Why would they act differently for HTTP and WebSocket?
> 
> 
> Few people serve their web apps from a DNS server.  Initially, virtually all
> WebSocket clients are going to be JS applications downloaded via HTTP.  If I
> am writing a JS game to be run in the browser, why would I want to maintain
> two servers instead of one?  Using Jetty (and I would expect most other
> servers to add support once the protocol is standardized), I can just add
> another method on my servlet and presto, I have WebSocket support.  This is
> especially important if the fallback is going to be hanging gets or polling
> via HTTP -- I can have common code for either solution, rather than
> duplicating code that runs in two separate servers, and it gets me the
> ability to more easily share state between HTTP requests and WebSocket
> messages, such as authentication credentials.

In fact, it seems clear that everyone understands how WS is going to be
used, except one person. Unfortunately, that person is the editor :-(

Willy