IETF Logo Mail Archive

Re: [hybi] Adding clarification regarding future revisions (Was: Proposed way forward for WebSockets)

Jamie Lokier <jamie@shareable.org> Tue, 27 July 2010 15:42 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 EEB7B3A69BC for <hybi@core3.amsl.com>; Tue, 27 Jul 2010 08:42:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.487
X-Spam-Level:
X-Spam-Status: No, score=-2.487 tagged_above=-999 required=5 tests=[AWL=0.112, 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 lqxlvBfZYUKq for <hybi@core3.amsl.com>; Tue, 27 Jul 2010 08:42:29 -0700 (PDT)
Received: from mail2.shareable.org (mail2.shareable.org [80.68.89.115]) by core3.amsl.com (Postfix) with ESMTP id 157593A680B for <hybi@ietf.org>; Tue, 27 Jul 2010 08:42:28 -0700 (PDT)
Received: from jamie by mail2.shareable.org with local (Exim 4.63) (envelope-from <jamie@shareable.org>) id 1OdmIo-0001qL-Om; Tue, 27 Jul 2010 16:42:46 +0100
Date: Tue, 27 Jul 2010 16:42:46 +0100
From: Jamie Lokier <jamie@shareable.org>
To: "Thomson, Martin" <Martin.Thomson@andrew.com>
Message-ID: <20100727154246.GF23142@shareable.org>
References: <ECF0E97F-1DA2-4662-BA48-F68B65AA8179@apple.com> <4C4D66AF.9030905@opera.com> <Pine.LNX.4.64.1007270030120.24444@ps20323.dreamhostps.com> <AANLkTi=fx=Yfm_pe9-pdCc=5sKRP=dNfDEBYCKNHFOmH@mail.gmail.com> <op.vghnjpex64w2qv@annevk-t60> <AANLkTik5AB=UPJ47z8tEnVygJodPVAmppeXUymMBz+9n@mail.gmail.com> <20100727065018.GA16134@1wt.eu> <Pine.LNX.4.64.1007270709300.3056@ps20323.dreamhostps.com> <AANLkTin9keorT4xSnAMnU8iS+TP+fqMQDkZSAh8jg7km@mail.gmail.com> <8B0A9FCBB9832F43971E38010638454F03EB773738@SISPE7MB1.commscope.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <8B0A9FCBB9832F43971E38010638454F03EB773738@SISPE7MB1.commscope.com>
User-Agent: Mutt/1.5.13 (2006-08-11)
Cc: "hybi@ietf.org" <hybi@ietf.org>
Subject: Re: [hybi] Adding clarification regarding future revisions (Was: Proposed way forward for WebSockets)
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, 27 Jul 2010 15:42:30 -0000

Thomson, Martin wrote:
> The nice thing is, if we stuff up websockets, we can always:
> 
> Upgrade: someotherprotocol
> 
> This goes for when we discover that we can't build an extension.

No, that doesn't work :-(

Think about when you want the browser to use some protocol extension
that is of no concern to the script writer, if and only if the server
supports it

What are you going to put in the Upgrade field that'll work with all
servers?

-- Jamie

v2.23.0 | Report a Bug | By Email