Re: [hybi] Websocket success rates and TLS extension.

Greg Wilkins <gregw@webtide.com> Sat, 17 April 2010 08:20 UTC

Return-Path: <gregw@webtide.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 956683A6A6D for <hybi@core3.amsl.com>; Sat, 17 Apr 2010 01:20:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.613
X-Spam-Level:
X-Spam-Status: No, score=-1.613 tagged_above=-999 required=5 tests=[AWL=0.986, 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 Bt7uTTjyQQoL for <hybi@core3.amsl.com>; Sat, 17 Apr 2010 01:20:32 -0700 (PDT)
Received: from mail-bw0-f225.google.com (mail-bw0-f225.google.com [209.85.218.225]) by core3.amsl.com (Postfix) with ESMTP id 22EED3A68E0 for <hybi@ietf.org>; Sat, 17 Apr 2010 01:20:31 -0700 (PDT)
Received: by bwz25 with SMTP id 25so3869072bwz.28 for <hybi@ietf.org>; Sat, 17 Apr 2010 01:20:21 -0700 (PDT)
Received: by 10.204.152.17 with SMTP id e17mr2478591bkw.105.1271492421059; Sat, 17 Apr 2010 01:20:21 -0700 (PDT)
Received: from [192.168.0.100] (host116-234-static.43-88-b.business.telecomitalia.it [88.43.234.116]) by mx.google.com with ESMTPS id 13sm2234835bwz.11.2010.04.17.01.20.20 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sat, 17 Apr 2010 01:20:20 -0700 (PDT)
Message-ID: <4BC96F43.3030806@webtide.com>
Date: Sat, 17 Apr 2010 10:20:19 +0200
From: Greg Wilkins <gregw@webtide.com>
User-Agent: Thunderbird 2.0.0.24 (X11/20100411)
MIME-Version: 1.0
To: Justin Erenkrantz <justin@erenkrantz.com>, "hybi@ietf.org" <hybi@ietf.org>
References: <4BBAECB7.2030009@webtide.com> <n2j5c902b9e1004170045if1df8e7atf67f926c1452996@mail.gmail.com>
In-Reply-To: <n2j5c902b9e1004170045if1df8e7atf67f926c1452996@mail.gmail.com>
X-Enigmail-Version: 0.95.7
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Subject: Re: [hybi] Websocket success rates and TLS extension.
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: Sat, 17 Apr 2010 08:20:35 -0000

Justin Erenkrantz wrote:

> I don't know how hard it is for Java servers to support TLS extensions
> - I'm sure you know, Greg.  =P  -- justin

It would probably need support from the JVM libraries before it
would be available to java programmers.   Potentially it could be
done with the current async SslEngine in java, but that's a difficult
beastie to deal with and even most infrastructure developers don't
go there.   But it strikes me as a reasonable optimization that
could be adopted over time.


The other idea I had on a similar RTT would be to allow the
101 response for an upgrade to contain a body.

This a browser could send

   GET /somethingUseful/andThenUpgrade
   Upgrade: WebSocket

and the response would return a useful entity, thus not wasting
a RT, and then upgrade after the response body.

Unfortunately I think this goes beyond the charter of
the current HTTPbis working group.

Cheers