Re: [hybi] [Uri-review] ws: and wss: schemes
Jamie Lokier <jamie@shareable.org> Thu, 20 August 2009 00:59 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 7BDB928C3D8 for <hybi@core3.amsl.com>; Wed, 19 Aug 2009 17:59:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.121
X-Spam-Level:
X-Spam-Status: No, score=-4.121 tagged_above=-999 required=5 tests=[AWL=-1.522, 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 FfbWNnaKlJsQ for <hybi@core3.amsl.com>; Wed, 19 Aug 2009 17:59:35 -0700 (PDT)
Received: from mail2.shareable.org (mail2.shareable.org [80.68.89.115]) by core3.amsl.com (Postfix) with ESMTP id 8C3A33A697C for <hybi@ietf.org>; Wed, 19 Aug 2009 17:59:35 -0700 (PDT)
Received: from jamie by mail2.shareable.org with local (Exim 4.63) (envelope-from <jamie@shareable.org>) id 1Mdw05-0003j0-1t; Thu, 20 Aug 2009 01:59:33 +0100
Date: Thu, 20 Aug 2009 01:59:33 +0100
From: Jamie Lokier <jamie@shareable.org>
To: Mark Nottingham <mnot@mnot.net>
Message-ID: <20090820005933.GA14005@shareable.org>
References: <OF22CD1320.96C55266-ON85257610.004AB599-85257610.004BC9CA@lotus.com> <C9931C12-E123-437D-8E7D-F8C680C62397@mnot.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <C9931C12-E123-437D-8E7D-F8C680C62397@mnot.net>
User-Agent: Mutt/1.5.13 (2006-08-11)
Cc: URI <uri@w3.org>, hybi@ietf.org
Subject: Re: [hybi] [Uri-review] ws: and wss: schemes
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, 20 Aug 2009 00:59:36 -0000
Fwiw, I agree with Mark that we should not be shy about using new schemes for new protocols that are not HTTP. Only things which run _over_ HTTP should use be using HTTP URIs, and WebSockets does not run over HTTP... but: Mark Nottingham wrote: > WebSockets is defining a protocol, and so is a very different case. It > is definitely not HTTP. That's correct, WebSockets is not HTTP. However it does begin with an HTTP connection and an HTTP request, to a server which may be serving other HTTP resources on the same port. Quite possibly over port 80, and in the process trip over HTTP proxies. So it's not really the same as telnet, FTP etc. Three notable things for which there is no consensus(*) are: 1. Does the WebSockets really have to use a fresh, new TCP connection for every individual instance of the WebSockets object created on every web page in a browser to the same site? Or could it upgrade an HTTP connection which has already been used for something else? 2. Since it begins with an HTTP request for upgrade to WebSockets, is there any reason for that request not to be to an arbitrary HTTP host+port+path by simply trying the upgrade method on the appropriate HTTP path at the server? 3. If a WebSockets connection cannot be established, clients will(**) fall back to an equivalent (but bulkier/slower) protocol which uses HTTP only. What URI will they use in that case? Do we leave it to individual application/framework designers, or do we suggest a common strategy? * - Although it has been asked if the protocol is a "politically agreed" foregone conclusion (due to an earlier message) and therefore if we are wasting our time with design discussions. ** - As in, even if the spec does not provide this and browsers do not provide it, there will certainly be Javascript WebSockets-emulation modules and corresponding server-sides which do. We can choose to ignore this and leave the mapping from WebSockets URI to HTTP-fallback URI unspecified, or recommend a mapping, or they can simply by the same URI given point 2. -- Jamie
- [hybi] ws: and wss: schemes Ian Hickson
- Re: [hybi] [Uri-review] ws: and wss: schemes Julian Reschke
- Re: [hybi] [Uri-review] ws: and wss: schemes Julian Reschke
- Re: [hybi] [Uri-review] ws: and wss: schemes Greg Wilkins
- Re: [hybi] [Uri-review] ws: and wss: schemes Ian Hickson
- Re: [hybi] [Uri-review] ws: and wss: schemes Maciej Stachowiak
- Re: [hybi] [Uri-review] ws: and wss: schemes Chris Anderson
- Re: [hybi] [Uri-review] ws: and wss: schemes Mark Nottingham
- Re: [hybi] [Uri-review] ws: and wss: schemes Pieter Hintjens
- Re: [hybi] [Uri-review] ws: and wss: schemes Jamie Lokier
- Re: [hybi] [Uri-review] ws: and wss: schemes Julian Reschke
- Re: [hybi] [Uri-review] ws: and wss: schemes David Booth
- Re: [hybi] [Uri-review] ws: and wss: schemes David Booth
- Re: [hybi] [Uri-review] ws: and wss: schemes Kristof Zelechovski
- Re: [hybi] [Uri-review] ws: and wss: schemes Kristof Zelechovski
- Re: [hybi] [Uri-review] ws: and wss: schemes Kristof Zelechovski
- Re: [hybi] [Uri-review] ws: and wss: schemes David Booth
- Re: [hybi] [Uri-review] ws: and wss: schemes Kristof Zelechovski
- Re: [hybi] [Uri-review] ws: and wss: schemes Greg Wilkins
- Re: [hybi] [Uri-review] ws: and wss: schemes Maciej Stachowiak
- Re: [hybi] [Uri-review] ws: and wss: schemes Jamie Lokier
- Re: [hybi] [Uri-review] ws: and wss: schemes Maciej Stachowiak
- Re: [hybi] [Uri-review] ws: and wss: schemes Maciej Stachowiak
- Re: [hybi] [Uri-review] ws: and wss: schemes Jamie Lokier
- Re: [hybi] [Uri-review] ws: and wss: schemes David Booth
- Re: [hybi] [Uri-review] ws: and wss: schemes David Orchard
- Re: [hybi] [Uri-review] ws: and wss: schemes Julian Reschke
- Re: [hybi] [Uri-review] ws: and wss: schemes Ian Hickson
- Re: [hybi] [Uri-review] ws: and wss: schemes Roy T. Fielding
- Re: [hybi] [Uri-review] ws: and wss: schemes Jamie Lokier
- Re: [hybi] [Uri-review] ws: and wss: schemes Jamie Lokier
- Re: [hybi] [Uri-review] ws: and wss: schemes Jamie Lokier
- Re: [hybi] [Uri-review] ws: and wss: schemes Julian Reschke
- Re: [hybi] [Uri-review] ws: and wss: schemes Ian Hickson
- Re: [hybi] [Uri-review] ws: and wss: schemes David Booth
- Re: [hybi] [Uri-review] ws: and wss: schemes Kristof Zelechovski
- Re: [hybi] [Uri-review] ws: and wss: schemes noah_mendelsohn
- Re: [hybi] [Uri-review] ws: and wss: schemes Toby Inkster
- Re: [hybi] [Uri-review] ws: and wss: schemes Křištof Želechovski
- Re: [hybi] [Uri-review] ws: and wss: schemes Jamie Lokier
- Re: [hybi] [Uri-review] ws: and wss: schemes Erik Wilde
- Re: [hybi] [Uri-review] ws: and wss: schemes noah_mendelsohn
- Re: [hybi] [Uri-review] ws: and wss: schemes Jamie Lokier
- Re: [hybi] [Uri-review] ws: and wss: schemes John Kemp
- Re: [hybi] [Uri-review] ws: and wss: schemes noah_mendelsohn
- Re: [hybi] [Uri-review] ws: and wss: schemes Mark Nottingham
- Re: [hybi] [Uri-review] ws: and wss: schemes Jamie Lokier
- Re: [hybi] [Uri-review] ws: and wss: schemes Erik Wilde
- Re: [hybi] [Uri-review] ws: and wss: schemes noah_mendelsohn
- Re: [hybi] [Uri-review] ws: and wss: schemes Jamie Lokier
- Re: [hybi] [Uri-review] ws: and wss: schemes noah_mendelsohn
- Re: [hybi] ws: and wss: schemes Ian Hickson
- Re: [hybi] ws: and wss: schemes Julian Reschke
- Re: [hybi] ws: and wss: schemes Ian Hickson
- Re: [hybi] ws: and wss: schemes Julian Reschke
- Re: [hybi] [Uri-review] ws: and wss: schemes Kristof Zelechovski
- Re: [hybi] ws: and wss: schemes Ian Hickson
- Re: [hybi] ws: and wss: schemes Julian Reschke
- Re: [hybi] [Uri-review] ws: and wss: schemes Julian Reschke
- Re: [hybi] [Uri-review] ws: and wss: schemes Julian Reschke
- Re: [hybi] ws: and wss: schemes Julian Reschke
- Re: [hybi] ws: and wss: schemes Ian Hickson
- Re: [hybi] [Uri-review] ws: and wss: schemes Jamie Lokier
- Re: [hybi] [Uri-review] ws: and wss: schemes Toby Inkster
- Re: [hybi] [Uri-review] ws: and wss: schemes David Booth
- Re: [hybi] [Uri-review] ws: and wss: schemes Kristof Zelechovski
- Re: [hybi] [Uri-review] ws: and wss: schemes Julian Reschke
- Re: [hybi] [Uri-review] ws: and wss: schemes Kristof Zelechovski
- Re: [hybi] ws: and wss: schemes Martin J. Dürst
- Re: [hybi] [Uri-review] ws: and wss: schemes David Booth
- Re: [hybi] [Uri-review] ws: and wss: schemes Toby Inkster
- Re: [hybi] [Uri-review] ws: and wss: schemes David Booth
- Re: [hybi] [Uri-review] ws: and wss: schemes Kristof Zelechovski
- Re: [hybi] [Uri-review] ws: and wss: schemes Martin J. Dürst
- Re: [hybi] [Uri-review] ws: and wss: schemes Křištof Želechovski
- Re: [hybi] [Uri-review] ws: and wss: schemes Jamie Lokier
- Re: [hybi] [Uri-review] ws: and wss: schemes Křištof Želechovski
- Re: [hybi] [Uri-review] ws: and wss: schemes Jamie Lokier
- Re: [hybi] [Uri-review] ws: and wss: schemes Joseph A Holsten
- Re: [hybi] [Uri-review] ws: and wss: schemes Joseph A Holsten
- Re: [hybi] [Uri-review] ws: and wss: schemes Joseph A Holsten
- Re: [hybi] [Uri-review] ws: and wss: schemes Daniel R. Tobias
- Re: [hybi] [Uri-review] ws: and wss: schemes Daniel R. Tobias
- Re: [hybi] [Uri-review] ws: and wss: schemes Daniel R. Tobias
- Re: [hybi] [Uri-review] ws: and wss: schemes Lisa Dusseault
- Re: [hybi] [Uri-review] ws: and wss: schemes Infinity Linden
- Re: [hybi] [Uri-review] ws: and wss: schemes Lloyd Wood
- Re: [hybi] [Uri-review] ws: and wss: schemes Kristof Zelechovski
- Re: [hybi] ws: and wss: schemes Ian Hickson
- Re: [hybi] ws: and wss: schemes Julian Reschke
- Re: [hybi] ws: and wss: schemes Ian Hickson
- Re: [hybi] ws: and wss: schemes Julian Reschke
- Re: [hybi] ws: and wss: schemes Julian Reschke
- Re: [hybi] ws: and wss: schemes Roy T. Fielding
- Re: [hybi] ws: and wss: schemes Julian Reschke
- Re: [hybi] [Uri-review] ws: and wss: schemes Martin J. Dürst
- Re: [hybi] ws: and wss: schemes Ian Hickson