IETF Logo Mail Archive

Re: [hybi] requirement: backwards compatible?. was : WebSocket feedback

Vladimir Katardjiev <vladimir@d2dx.com> Wed, 10 March 2010 13:24 UTC

Return-Path: <vladimir@d2dx.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 3E33B3A69F6 for <hybi@core3.amsl.com>; Wed, 10 Mar 2010 05:24:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, 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 vsD0fppfAmDo for <hybi@core3.amsl.com>; Wed, 10 Mar 2010 05:24:22 -0800 (PST)
Received: from homiemail-a1.g.dreamhost.com (mailbigip.dreamhost.com [208.97.132.5]) by core3.amsl.com (Postfix) with ESMTP id 8AA783A6912 for <hybi@ietf.org>; Wed, 10 Mar 2010 05:24:22 -0800 (PST)
Received: from dhcp122.verkstad.net (dhcp122.verkstad.net [192.36.157.122]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by homiemail-a1.g.dreamhost.com (Postfix) with ESMTP id ACD3E119DC3; Wed, 10 Mar 2010 05:24:26 -0800 (PST)
Mime-Version: 1.0 (Apple Message framework v1077)
Content-Type: multipart/signed; boundary="Apple-Mail-1-9970895"; protocol="application/pkcs7-signature"; micalg="sha1"
From: Vladimir Katardjiev <vladimir@d2dx.com>
In-Reply-To: <4B975287.3030808@webtide.com>
Date: Wed, 10 Mar 2010 14:24:23 +0100
Message-Id: <6B238154-9532-4A1C-8B1B-8D6A81999253@d2dx.com>
References: <8B0A9FCBB9832F43971E38010638454F032E566DDF@SISPE7MB1.commscope.com> <Pine.LNX.4.64.1002150605580.29686@ps20323.dreamhostps.com> <4B975287.3030808@webtide.com>
To: Hybi <hybi@ietf.org>
X-Mailer: Apple Mail (2.1077)
Subject: Re: [hybi] requirement: backwards compatible?. was : WebSocket feedback
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, 10 Mar 2010 13:24:23 -0000

On 10 mar 2010, at 09.04, Greg Wilkins wrote:

> All,
> 
> Is there some plan to transition from the browsers that support
> the current draft to the browsers that support the document that
> is produced as a result of this process?
> 
> Is it a requirement that we consider backwards compatibility to
> the solutions already being shipped?
> 
> Obviously there will have to be some breakage, but currently
> without any version information that could be hard to handle.
> Even if we use Sec headers to infer versions, we need to define
> behaviour for miss-matched versions.

Strictly speaking, behaviour of version mismatch is failed handshake, and the client/server should disconnect. For socket access to the protocol this is easy to identify, detect and log. It's a bit harder from within a browser, though. (is there any handy way to see if/when chromium/webkit include new revision of WS?)

Cheers,
Vladimir

v2.23.0 | Report a Bug | By Email